CVE-2005-2729
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 HTTP proxy in Astaro Security Linux 6.0 does not properly filter HTTP CONNECT requests to localhost, which allows remote attackers to bypass firewall rules and connect to local services.
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 · moderate confidenceThe HTTP proxy in Astaro Security Linux 6.0 fails to restrict HTTP CONNECT method requests to localhost addresses (127.0.0.1). This allows remote attackers through the proxy to bypass firewall protections and establish direct connections to internal services listening only on localhost, such as web interfaces, databases, or administrative services.
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= 6.001CVSS 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.
-
Verify Astaro Security Linux versionCheck the installed operating system version by examining /etc/os-release, /etc/astaro-release, or running 'uname -a' and 'cat /proc/version'Affected if The system is running Astaro Security Linux version 6.001 exactly (or a version within the 6.0x range)
-
Identify if HTTP proxy service is installedLook for proxy-related processes and services using commands like 'ps aux | grep -i proxy', 'service --status-all', or checking for packages such as squid, dansguardian, or astaro-http-proxyAffected if An HTTP proxy service (typically Squid or Astaro's own proxy) is installed and running on the system
-
Locate the HTTP proxy configuration filesSearch for proxy configuration in common locations: /etc/squid/, /etc/squid3/, /etc/dansguardian/, /opt/astaro/, or check the Astaro command center for proxy settingsAffected if Proxy configuration files exist on the system indicating the proxy feature is enabled
-
Check CONNECT method access control rulesExamine the proxy configuration files for rules controlling the CONNECT method, specifically looking for 'acl' directives and 'http_access' rules that may permit or deny connections to localhost (127.0.0.1)Affected if The proxy configuration allows CONNECT method requests to 127.0.0.1 or contains no explicit rule blocking localhost connections
-
Verify firewall interaction with proxyReview iptables rules and Astaro security gateway settings to confirm the proxy can be accessed by remote clients and is not blocked from forwarding traffic to localhost-bound servicesAffected if The firewall permits proxy traffic to reach internal services bound to 127.0.0.1 through the proxy
A system is affected if it runs Astaro Security Linux 6.001 with the HTTP proxy enabled and the CONNECT method is permitted to reach localhost addresses without explicit restriction.
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 dataConfigure the HTTP proxy to deny or restrict CONNECT requests to localhost (127.0.0.1), internal network ranges, and loopback addresses. Implement access control lists that explicitly block proxy connections to local/internal addresses.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2729 — 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-2005-2729 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