Skip to main content
Mallory
LowPublic exploitVulnerability

CVE-2002-1983: Timer DoS and Potential Code Execution in QNX RTOS 6.1.0

Published Jun 28, 2005 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS2.1Low · v2
EPSS0.99%63rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
QNX Software Systems
IdentifiersCVE-2002-1983CWE-400

A vulnerability in the timer implementation of QNX RTOS 6.1.0 allows local users to create multiple timers with a 1-ms tick, which can lead to a system hang (denial of service) and potentially allow arbitrary code execution. The flaw is due to improper handling of timer resources and scheduling, which can be exploited by a local attacker to exhaust system resources or trigger undefined behavior.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local attacker to cause a denial of service by hanging the system. There is also a possibility of arbitrary code execution, which could lead to full system compromise if the attacker is able to leverage the flaw beyond resource exhaustion.

Mitigation

If you can’t patch tonight, do this now.

Restrict local access to trusted users only. Monitor and limit the creation of timers by untrusted processes. Apply any available patches or workarounds from the vendor.

Remediation

Patch, then assume compromise.

Upgrade to a version of QNX RTOS where the timer implementation has been fixed to properly handle multiple timers with small tick intervals. Consult vendor advisories for patches or mitigations.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
QNX Software SystemsRtosapplication
FAQ

Frequently asked questions

Is CVE-2002-1983 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2002-1983 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2002-1983?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2002-1983.
Is there a patch for CVE-2002-1983?
Upgrade to a version of QNX RTOS where the timer implementation has been fixed to properly handle multiple timers with small tick intervals. Consult vendor advisories for patches or mitigations.
What products are affected by CVE-2002-1983?
QNX Software Systems Rtos.
How severe is CVE-2002-1983?
CVE-2002-1983 has a CVSS v2 score of 2.1 (Low) and an EPSS score of 0.99% (63rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.