What is the severity of CVE-2004-0530?

CVE-2004-0530 is considered a high severity vulnerability due to the potential for local users to execute arbitrary code.

How do I fix CVE-2004-0530?

To fix CVE-2004-0530, upgrade the PHP package to a version not affected by this vulnerability on Slackware.

Who is affected by CVE-2004-0530?

CVE-2004-0530 affects users of Slackware Linux versions 8.1, 9.0, and 9.1 when linked against a static library.

What could an attacker do exploiting CVE-2004-0530?

An attacker could exploit CVE-2004-0530 to execute arbitrary code as the PHP user, compromising the system.

Is there a workaround for CVE-2004-0530 if I cannot upgrade?

A possible workaround for CVE-2004-0530 is to remove /tmp from the library search path, but this is not a complete fix.

Vulnerability/
CVE-2004-0530

high

7.2

CWE

NVD-CWE-Other

8/6/2004

8/8/2024

CVE-2004-0530

First published: Tue Jun 08 2004(Updated: )

The PHP package in Slackware 8.1, 9.0, and 9.1, when linked against a static library, includes /tmp in the search path, which allows local users to execute arbitrary code as the PHP user by inserting shared libraries into the appropriate path.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Slackware Slackware Linux	=9.0
Slackware Slackware Linux	=8.1
Slackware Slackware Linux	=9.1
Slackware Linux	=8.1
Slackware Linux	=9.0
Slackware Linux	=9.1

Remedy

http://www.slackware.com/security/viewer.php?l=slackware-security&y=2004&m=slackware-security.419765

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2004-0530?
CVE-2004-0530 is considered a high severity vulnerability due to the potential for local users to execute arbitrary code.
How do I fix CVE-2004-0530?
To fix CVE-2004-0530, upgrade the PHP package to a version not affected by this vulnerability on Slackware.
Who is affected by CVE-2004-0530?
CVE-2004-0530 affects users of Slackware Linux versions 8.1, 9.0, and 9.1 when linked against a static library.
What could an attacker do exploiting CVE-2004-0530?
An attacker could exploit CVE-2004-0530 to execute arbitrary code as the PHP user, compromising the system.
Is there a workaround for CVE-2004-0530 if I cannot upgrade?
A possible workaround for CVE-2004-0530 is to remove /tmp from the library search path, but this is not a complete fix.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/remedy
agent/weakness
agent/author
agent/last-modified-date
agent/severity
agent/description
agent/event
agent/first-publish-date
agent/source
agent/softwarecombine
collector/nvd-historical
agent/software-canonical-lookup-request
agent/tags
collector/nvd-index
vendor/slackware
canonical/slackware slackware linux
version/slackware slackware linux/9.0
version/slackware slackware linux/8.1
version/slackware slackware linux/9.1
canonical/slackware linux
version/slackware linux/8.1
version/slackware linux/9.0
version/slackware linux/9.1

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.