What is the severity of CVE-2002-2039?

CVE-2002-2039 has a moderate severity level, as it allows local users to access sensitive information.

How do I fix CVE-2002-2039?

To fix CVE-2002-2039, upgrade to a patched version of QNX RTOS that addresses this vulnerability.

Who is affected by CVE-2002-2039?

Local users of QNX RTOS versions 4.25 and 6.1.0 are affected by CVE-2002-2039.

What does CVE-2002-2039 exploit?

CVE-2002-2039 exploits the handling of core dump files by the /bin/su command in QNX RTOS.

Is CVE-2002-2039 a remote attack vector?

No, CVE-2002-2039 is a local vulnerability, meaning it can only be exploited by users with local access to the system.

Vulnerability/
CVE-2002-2039

low

2.1

CWE

NVD-CWE-Other

31/12/2002

14/7/2005

8/8/2024

CVE-2002-2039

First published: Tue Dec 31 2002(Updated: )

/bin/su in QNX realtime operating system (RTOS) 4.25 and 6.1.0 allows local users to obtain sensitive information from core dump files by sending the SIGSERV (invalid memory reference) signal.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
QNX RTOS	=4.25
QNX RTOS	=6.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-2039?
CVE-2002-2039 has a moderate severity level, as it allows local users to access sensitive information.
How do I fix CVE-2002-2039?
To fix CVE-2002-2039, upgrade to a patched version of QNX RTOS that addresses this vulnerability.
Who is affected by CVE-2002-2039?
Local users of QNX RTOS versions 4.25 and 6.1.0 are affected by CVE-2002-2039.
What does CVE-2002-2039 exploit?
CVE-2002-2039 exploits the handling of core dump files by the /bin/su command in QNX RTOS.
Is CVE-2002-2039 a remote attack vector?
No, CVE-2002-2039 is a local vulnerability, meaning it can only be exploited by users with local access to the system.

collector/nvd-historical
vendor/qnx
product/rtos
canonical/qnx rtos
collector/nvd-index
agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/weakness
agent/references
agent/last-modified-date
agent/description
agent/event
agent/tags
agent/source
version/qnx rtos/4.25
version/qnx rtos/6.1.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2002-2039?
CVE-2002-2039 has a moderate severity level, as it allows local users to access sensitive information.
How do I fix CVE-2002-2039?
To fix CVE-2002-2039, upgrade to a patched version of QNX RTOS that addresses this vulnerability.
Who is affected by CVE-2002-2039?
Local users of QNX RTOS versions 4.25 and 6.1.0 are affected by CVE-2002-2039.
What does CVE-2002-2039 exploit?
CVE-2002-2039 exploits the handling of core dump files by the /bin/su command in QNX RTOS.
Is CVE-2002-2039 a remote attack vector?
No, CVE-2002-2039 is a local vulnerability, meaning it can only be exploited by users with local access to the system.