What is the severity of CVE-2004-1683?

CVE-2004-1683 is considered a high severity vulnerability due to the risk of privilege escalation.

How do I fix CVE-2004-1683?

To mitigate CVE-2004-1683, ensure that the PATH environment variable is secure and does not point to any untrusted locations before executing crrtrap.

What systems are affected by CVE-2004-1683?

CVE-2004-1683 affects users of QNX RTP version 6.1 and earlier versions of QNX RTOS such as 6.2.0 and 6.2.0a.

Can I still use QNX RTP 6.1 if CVE-2004-1683 is present?

Using QNX RTP 6.1 is risky due to CVE-2004-1683, and it is recommended to upgrade to a patched version.

Who is vulnerable to CVE-2004-1683?

Local users of QNX RTP 6.1 can exploit CVE-2004-1683 to gain unauthorized privileges.

Vulnerability/
CVE-2004-1683

low

3.7

CWE

NVD-CWE-Other 362

13/9/2004

20/2/2005

8/8/2024

CVE-2004-1683: Race Condition

First published: Mon Sep 13 2004(Updated: )

A race condition in crrtrap for QNX RTP 6.1 allows local users to gain privileges by modifying the PATH environment variable to reference a malicious io-graphics program before is executed by crrtrap.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
QNX RTOS	=6.2.0
QNX RTOS	=6.2.0a
QNX RTOS	=6.2.0
QNX RTOS	=6.2.0a

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2004-1683?
CVE-2004-1683 is considered a high severity vulnerability due to the risk of privilege escalation.
How do I fix CVE-2004-1683?
To mitigate CVE-2004-1683, ensure that the PATH environment variable is secure and does not point to any untrusted locations before executing crrtrap.
What systems are affected by CVE-2004-1683?
CVE-2004-1683 affects users of QNX RTP version 6.1 and earlier versions of QNX RTOS such as 6.2.0 and 6.2.0a.
Can I still use QNX RTP 6.1 if CVE-2004-1683 is present?
Using QNX RTP 6.1 is risky due to CVE-2004-1683, and it is recommended to upgrade to a patched version.
Who is vulnerable to CVE-2004-1683?
Local users of QNX RTP 6.1 can exploit CVE-2004-1683 to gain unauthorized privileges.

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

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-2004-1683?
CVE-2004-1683 is considered a high severity vulnerability due to the risk of privilege escalation.
How do I fix CVE-2004-1683?
To mitigate CVE-2004-1683, ensure that the PATH environment variable is secure and does not point to any untrusted locations before executing crrtrap.
What systems are affected by CVE-2004-1683?
CVE-2004-1683 affects users of QNX RTP version 6.1 and earlier versions of QNX RTOS such as 6.2.0 and 6.2.0a.
Can I still use QNX RTP 6.1 if CVE-2004-1683 is present?
Using QNX RTP 6.1 is risky due to CVE-2004-1683, and it is recommended to upgrade to a patched version.
Who is vulnerable to CVE-2004-1683?
Local users of QNX RTP 6.1 can exploit CVE-2004-1683 to gain unauthorized privileges.