LinuxOperating system · Redhat
CVE-1999-0710
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Squid package in Red Hat Linux 5.2 and 6.0, and other distributions, installs cachemgr.cgi in a public web directory, which allows remote attackers to use it as an intermediary to connect to other systems.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Squid proxy server package for Red Hat Linux 5.2 and 6.0 (and other distributions) installed the cachemgr.cgi management script in a publicly accessible web directory. This allowed remote attackers to access the CGI and use the Squid server as an open proxy intermediary to relay connections to other internal or external systems, facilitating attacks or evasion of network restrictions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LinuxOperating system
= 5.2= 6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Squid proxy server is installedRun 'rpm -qa | grep squid' on Red Hat-based systems, or check for squid process with 'ps aux | grep squid'Affected if Squid package is installed and running
-
Locate cachemgr.cgi on the systemSearch for cachemgr.cgi using 'find / -name cachemgr.cgi 2>/dev/null'Affected if cachemgr.cgi file exists on the system
-
Identify web server document root and CGI directoriesCheck common web directories like /var/www/cgi-bin/, /usr/local/squid/libexec/, or /etc/httpd/conf/httpd.conf for CGI script locationsAffected if cachemgr.cgi is located in a web-accessible directory (typically /var/www/cgi-bin/ or similar)
-
Test external access to cachemgr.cgiUse a web browser or curl to request http://your-server/cgi-bin/cachemgr.cgi from an untrusted network or IPAffected if The CGI is accessible without authentication and returns a Squid cache manager interface
-
Verify web server authentication is not configured for cachemgr.cgiReview Apache or web server config files for ScriptAlias or Location directives protecting /cgi-bin/cachemgr.cgi with auth requirementsAffected if No authentication (Basic, Digest, or other) is required to access cachemgr.cgi, or no IP-based access controls exist
A user is affected if Squid is installed and cachemgr.cgi is present in a publicly accessible web directory without authentication or IP restrictions, allowing unauthorized relay of connections through the Squid server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove cachemgr.cgi from public web directories if the Squid cache manager interface is not required, or restrict access to it via web server authentication or IP-based access controls.
Fix this in Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-0710 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data