CVE-2002-1983
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang)...
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang) and possibly execute arbitrary code by creating multiple timers with a 1-ms tick.
Exploit likelihood
What each source reports
NVD Score used
2.1
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang) and possibly execute arbitrary code by creating multiple timers with a 1-ms tick.
- Record
CVE-2002-1983- CVSS 2.0
- 2.1 Low
AV:L/AC:L/Au:N/C:N/I:N/A:P - Updated
- 2026-11-02
CVE List No score
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang) and possibly execute arbitrary code by creating multiple timers with a 1-ms tick.
- Record
CVE-2002-1983- Updated
- 2026-11-02
EUVDEUVD-2002-1962 No score
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang) and possibly execute arbitrary code by creating multiple timers with a 1-ms tick.
- Record
EUVD-2002-1962- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-87p5-fx33-2fh8 No score
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang)...
The timer implementation in QNX RTOS 6.1.0 allows local users to cause a denial of service (hang) and possibly execute arbitrary code by creating multiple timers with a 1-ms tick.
- Record
GHSA-87p5-fx33-2fh8- Updated
- 2026-11-02
Affected products
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | QNX 6.1 - 'TimeCreate' Local Denial of Service | 2002-11-06 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2002-1983 is a low vulnerability (CVSS 2.1) in Qnx Rtos, published December 31, 2002. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 0.99%, the 62nd percentile. No source names a fixed version.