CVE-2002-2180
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments...
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments, which allows local users to write to kernel memory and possibly gain root privileges, possibly via an integer signedness error.
Exploit likelihood
What each source reports
NVD Score used
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments, which allows local users to write to kernel memory and possibly gain root privileges, possibly via an integer signedness error.
- Record
CVE-2002-2180- CVSS 2.0
- 6.8 Medium
AV:L/AC:L/Au:S/C:C/I:C/A:C - Updated
- 2026-11-02
CVE List No score
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments, which allows local users to write to kernel memory and possibly gain root privileges, possibly via an integer signedness error.
- Record
CVE-2002-2180- Updated
- 2026-11-02
EUVDEUVD-2002-2159 No score
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments, which allows local users to write to kernel memory and possibly gain root privileges, possibly via an integer signedness error.
- Record
EUVD-2002-2159- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-fqm4-g2w4-w349 No score
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments...
The setitimer(2) system call in OpenBSD 2.0 through 3.1 does not properly check certain arguments, which allows local users to write to kernel memory and possibly gain root privileges, possibly via an integer signedness error.
- Record
GHSA-fqm4-g2w4-w349- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2002-2180 is a medium vulnerability (CVSS 6.8) in Openbsd, published December 31, 2002. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.61%, the 49th percentile. No source names a fixed version.