What is the severity of CVE-1999-0475?

The severity of CVE-1999-0475 is generally considered to be medium due to the potential for local users to read sensitive files.

How do I fix CVE-1999-0475?

To fix CVE-1999-0475, ensure that appropriate file permissions are set on .procmailrc files and consider updating to the latest version of procmail.

Who is affected by CVE-1999-0475?

CVE-1999-0475 affects local users running procmail who can access the .procmailrc file.

What type of vulnerability is CVE-1999-0475?

CVE-1999-0475 is classified as a race condition vulnerability.

What can an attacker do with CVE-1999-0475?

An attacker can exploit CVE-1999-0475 to read arbitrary files that are accessible to the user executing procmail.

Vulnerability/
CVE-1999-0475

low

1.2

CWE

NVD-CWE-Other 362

5/4/1999

29/9/1999

20/11/2024

CVE-1999-0475: Race Condition

First published: Mon Apr 05 1999(Updated: )

A race condition in how procmail handles .procmailrc files allows a local user to read arbitrary files available to the user who is running procmail.

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

Affected Software	Affected Version	How to fix
procmail

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-1999-0475?
The severity of CVE-1999-0475 is generally considered to be medium due to the potential for local users to read sensitive files.
How do I fix CVE-1999-0475?
To fix CVE-1999-0475, ensure that appropriate file permissions are set on .procmailrc files and consider updating to the latest version of procmail.
Who is affected by CVE-1999-0475?
CVE-1999-0475 affects local users running procmail who can access the .procmailrc file.
What type of vulnerability is CVE-1999-0475?
CVE-1999-0475 is classified as a race condition vulnerability.
What can an attacker do with CVE-1999-0475?
An attacker can exploit CVE-1999-0475 to read arbitrary files that are accessible to the user executing procmail.

agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/references
agent/description
agent/last-modified-date
agent/author
agent/softwarecombine
agent/event
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/procmail
product/procmail
canonical/procmail procmail
collector/nvd-index
canonical/procmail

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-0475?
The severity of CVE-1999-0475 is generally considered to be medium due to the potential for local users to read sensitive files.
How do I fix CVE-1999-0475?
To fix CVE-1999-0475, ensure that appropriate file permissions are set on .procmailrc files and consider updating to the latest version of procmail.
Who is affected by CVE-1999-0475?
CVE-1999-0475 affects local users running procmail who can access the .procmailrc file.
What type of vulnerability is CVE-1999-0475?
CVE-1999-0475 is classified as a race condition vulnerability.
What can an attacker do with CVE-1999-0475?
An attacker can exploit CVE-1999-0475 to read arbitrary files that are accessible to the user executing procmail.