What is the severity of CVE-2005-4082?

CVE-2005-4082 is considered a high severity vulnerability due to its potential for local users to exploit setuid permissions.

How do I fix CVE-2005-4082?

To fix CVE-2005-4082, remove the setuid bit from the dhcp.client program or apply updates from QNX that address this issue.

Who is affected by CVE-2005-4082?

CVE-2005-4082 affects users of QNX version 4.25 where the dhcp.client program is setuid.

What types of attacks can be conducted due to CVE-2005-4082?

Due to CVE-2005-4082, local users can modify network interface configurations and potentially escalate privileges.

Is CVE-2005-4082 still a concern in modern systems?

CVE-2005-4082 primarily impacts legacy systems running QNX 4.25 and is less of a concern in contemporary environments.

Vulnerability/
CVE-2005-4082

medium

4.6

CWE

NVD-CWE-Other

8/12/2005

7/8/2024

CVE-2005-4082

First published: Thu Dec 08 2005(Updated: )

The dhcp.client program for QNX 4.25 vmware is setuid, possibly by default, which allows local users to modify the NIC configuration and conduct other attacks.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Qnx Qnx	=4.25

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-4082?
CVE-2005-4082 is considered a high severity vulnerability due to its potential for local users to exploit setuid permissions.
How do I fix CVE-2005-4082?
To fix CVE-2005-4082, remove the setuid bit from the dhcp.client program or apply updates from QNX that address this issue.
Who is affected by CVE-2005-4082?
CVE-2005-4082 affects users of QNX version 4.25 where the dhcp.client program is setuid.
What types of attacks can be conducted due to CVE-2005-4082?
Due to CVE-2005-4082, local users can modify network interface configurations and potentially escalate privileges.
Is CVE-2005-4082 still a concern in modern systems?
CVE-2005-4082 primarily impacts legacy systems running QNX 4.25 and is less of a concern in contemporary environments.

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

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-2005-4082?
CVE-2005-4082 is considered a high severity vulnerability due to its potential for local users to exploit setuid permissions.
How do I fix CVE-2005-4082?
To fix CVE-2005-4082, remove the setuid bit from the dhcp.client program or apply updates from QNX that address this issue.
Who is affected by CVE-2005-4082?
CVE-2005-4082 affects users of QNX version 4.25 where the dhcp.client program is setuid.
What types of attacks can be conducted due to CVE-2005-4082?
Due to CVE-2005-4082, local users can modify network interface configurations and potentially escalate privileges.
Is CVE-2005-4082 still a concern in modern systems?
CVE-2005-4082 primarily impacts legacy systems running QNX 4.25 and is less of a concern in contemporary environments.