What is the severity of CVE-1999-0122?

CVE-1999-0122 is classified as a critical vulnerability due to the buffer overflow allowing root access.

How do I fix CVE-1999-0122?

To fix CVE-1999-0122, it is recommended to apply the latest patches provided by IBM for AIX versions 4.1.x and 4.2.

What AIX versions are affected by CVE-1999-0122?

CVE-1999-0122 affects IBM AIX versions 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, and 4.2.

What are the potential impacts of exploiting CVE-1999-0122?

Exploitation of CVE-1999-0122 can lead to unauthorized root access, compromising the integrity and security of the system.

Is there a workaround for CVE-1999-0122?

While the most effective solution is to apply patches, restricting access to the affected lchangelv command can serve as a temporary workaround.

Vulnerability/
CVE-1999-0122

high

7.2

CWE

NVD-CWE-Other 119

21/7/1997

29/9/1999

20/11/2024

CVE-1999-0122: Buffer Overflow

First published: Mon Jul 21 1997(Updated: )

Buffer overflow in AIX lchangelv gives root access.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
IBM AIX	=4.1.4
IBM AIX	=4.2
IBM AIX	=4.1.5
IBM AIX	=4.1.1
IBM AIX	=4.1.2
IBM AIX	=4.1
IBM AIX	=4.1.3
	=4.1
	=4.1.1
	=4.1.2
	=4.1.3
	=4.1.4
	=4.1.5
	=4.2

Never miss a vulnerability like this again

Reference Links

https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0122

Frequently Asked Questions

What is the severity of CVE-1999-0122?
CVE-1999-0122 is classified as a critical vulnerability due to the buffer overflow allowing root access.
How do I fix CVE-1999-0122?
To fix CVE-1999-0122, it is recommended to apply the latest patches provided by IBM for AIX versions 4.1.x and 4.2.
What AIX versions are affected by CVE-1999-0122?
CVE-1999-0122 affects IBM AIX versions 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, and 4.2.
What are the potential impacts of exploiting CVE-1999-0122?
Exploitation of CVE-1999-0122 can lead to unauthorized root access, compromising the integrity and security of the system.
Is there a workaround for CVE-1999-0122?
While the most effective solution is to apply patches, restricting access to the affected lchangelv command can serve as a temporary workaround.

collector/nvd-historical
collector/nvd-index
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/weakness
agent/description
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/author
agent/softwarecombine
agent/event
agent/tags
agent/source
vendor/ibm
canonical/ibm aix
version/ibm aix/4.1.4
version/ibm aix/4.2
version/ibm aix/4.1.5
version/ibm aix/4.1.1
version/ibm aix/4.1.2
version/ibm aix/4.1
version/ibm aix/4.1.3

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-1999-0122?
CVE-1999-0122 is classified as a critical vulnerability due to the buffer overflow allowing root access.
How do I fix CVE-1999-0122?
To fix CVE-1999-0122, it is recommended to apply the latest patches provided by IBM for AIX versions 4.1.x and 4.2.
What AIX versions are affected by CVE-1999-0122?
CVE-1999-0122 affects IBM AIX versions 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, and 4.2.
What are the potential impacts of exploiting CVE-1999-0122?
Exploitation of CVE-1999-0122 can lead to unauthorized root access, compromising the integrity and security of the system.
Is there a workaround for CVE-1999-0122?
While the most effective solution is to apply patches, restricting access to the affected lchangelv command can serve as a temporary workaround.