dbcve.org
RtosApplication · Qnx

CVE-2002-2407

MEDIUM · 6.9 CVSS v2.0 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain patches for QNX Neutrino realtime operating system (RTOS) 6.2.0 set insecure permissions for the files (1) /sbin/io-audio by OS Update Patch A, (2) /bin/shutdown, (3) /sbin/fs-pkg, and (4) phshutdown by QNX experimental patches, (5) cpim, (6) vpim, (7) phrelaycfg, and (8) columns, (9) othello, (10) peg, (11) solitaire, and (12) vpoker in the games pack 2.0.3, which allows local users to gain privileges by modifying the files before permissions are changed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Certain patches for QNX Neutrino RTOS 6.2.0 set insecure file permissions (likely world-writable or insecure ownership) on multiple system binaries including /sbin/io-audio, /bin/shutdown, /sbin/fs-pkg, phshutdown, and several application binaries (cpim, vpim, phrelaycfg, columns) and games (othello, peg, solitaire, vpoker). This allows local users to modify these files before proper permissions are applied, enabling local privilege escalation.

MitigationImmediately audit and correct file permissions on all affected binaries to restrictive ownership (root) and appropriate permissions (755 for binaries, 755 for directories). Verify no unauthorized modifications have occurred and reapply patches if needed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RtosApplication
Affected:= 6.2= 6.2a

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify QNX Neutrino RTOS version
    Run 'uname -a' or check /etc/version or use 'sin ver' command to confirm the installed QNX Neutrino version is 6.2 or 6.2a
    Affected if The system is running QNX Neutrino RTOS version 6.2 or 6.2a
  2. Check permissions on /sbin/io-audio
    Run 'ls -la /sbin/io-audio' to inspect file permissions and ownership
    Affected if The file is world-writable (permissions include 'w' for 'others') or owned by a non-root user
  3. Check permissions on /bin/shutdown and /sbin/fs-pkg
    Run 'ls -la /bin/shutdown /sbin/fs-pkg' to inspect permissions and ownership of these critical system binaries
    Affected if Either file is world-writable or owned by a non-root user
  4. Check permissions on phshutdown and application binaries
    Run 'ls -la /path/to/phshutdown /path/to/cpim /path/to/vpim /path/to/phrelaycfg /path/to/columns' (adjust paths as needed) to inspect permissions
    Affected if Any of these binaries are world-writable or have insecure ownership
  5. Check permissions on game binaries
    Run 'ls -la /path/to/othello /path/to/peg /path/to/solitaire /path/to/vpoker' to inspect permissions on the listed games
    Affected if Any game binary is world-writable or owned by a non-root user
  6. Audit for recent patch application
    Review system patch logs or check file timestamps on the affected binaries to determine if patches from QNX have been recently applied
    Affected if Patches were recently applied and the binaries now exhibit world-writable permissions

A system is affected if it is running QNX Neutrino RTOS 6.2 or 6.2a with any of the listed binaries (io-audio, shutdown, fs-pkg, phshutdown, cpim, vpim, phrelaycfg, columns, othello, peg, solitaire, vpoker) having world-writable permissions or non-root ownership after patch application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately audit and correct file permissions on all affected binaries to restrictive ownership (root) and appropriate permissions (755 for binaries, 755 for directories). Verify no unauthorized modifications have occurred and reapply patches if needed.

Fix this in Rtos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-2407 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data