Menu

Star on GitHub · 3.2k

CVE-2005-4273

2.1 · LOW

Multiple unspecified vulnerabilities in (1) getShell and (2) getCommand in IBM AIX 5.3 allow local users to append to arbitrary files.

Published Dec 15, 2005ibmEPSS 0.38%

Overview

CVE-2005-4273 is a low-severity vulnerability affecting ibm aix. It was published on December 15, 2005 and has a CVSS 2.0 base score of 2.1 (LOW).

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Multiple unspecified vulnerabilities in (1) getShell and (2) getCommand in IBM AIX 5.3 allow local users to append to arbitrary files.

Remediation

Check the references section for vendor advisories and patches from ibm. Update aix to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2005-4273?

CVE-2005-4273 is a low-severity vulnerability affecting ibm aix. It was published on December 15, 2005 and has a CVSS 2.0 base score of 2.1 (LOW).

How severe is CVE-2005-4273?

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-4273?

Check the references section for vendor advisories and patches from ibm. Update aix to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-4273?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-4273 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2005

View all