CVE-2011-2667
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 · uneditedIcihttp.exe in CA Gateway Security for HTTP, as used in CA Gateway Security 8.1 before 8.1.0.69 and CA Total Defense r12, does not properly parse URLs, which allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption and daemon crash) via a malformed request.
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 icihttp.exe component in CA Gateway Security 8.1 before 8.1.0.69 and CA Total Defense r12 fails to properly parse malformed URLs in incoming HTTP requests. This improper parsing leads to heap memory corruption, enabling remote attackers to execute arbitrary code or cause a denial of service via crafted requests.
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= r12= 8.1CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Confirm CA product installationLocate CA Gateway Security or CA Total Defense installations on the system - check Program Files for CA directories, or query installed software via system inventory toolsAffected if Neither CA Gateway Security nor CA Total Defense is installed
-
Identify product versionCheck the installed version of CA Gateway Security (expected 8.1.x) or CA Total Defense (expected r12) - look in the product's about or version information panelAffected if Version is 8.1 before 8.1.0.69 for CA Gateway Security, or r12 for CA Total Defense
-
Locate icihttp.exe componentFind the icihttp.exe binary within the CA product installation directory - this is the vulnerable component that handles HTTP parsingAffected if icihttp.exe is present and matches a version prior to 8.1.0.69
-
Verify HTTP service exposureConfirm the icihttp.exe HTTP service is listening on network ports (typically ports 80/443 or configured HTTP ports) and accessible from networkAffected if HTTP service is exposed and accessible to untrusted traffic without sanitization
A system is affected if it runs CA Gateway Security 8.1 before 8.1.0.69 or CA Total Defense r12 with the icihttp.exe component exposed to incoming HTTP requests.
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.
dbcve · scopedApply vendor patch 8.1.0.69 or later to address the URL parsing vulnerability. If patching is not feasible, implement request filtering or place the gateway behind a reverse proxy that sanitizes malformed URLs before they reach the vulnerable component.
CA Gateway Security 8.1.0.69 or later; Total Defense r12 - contact vendor for patched release
- 1. Identify the exact version of CA Gateway Security or Total Defense r12 currently installed
- 2. For CA Gateway Security 8.1: Upgrade to version 8.1.0.69 or later which contains the fix for the URL parsing vulnerability in Icihttp.exe
- 3. For Total Defense r12: Contact CA (Broadcom) support to obtain the specific patched release that addresses CVE-2011-2667
- 4. After upgrading, verify the Icihttp.exe service is running properly
- 5. Test that normal HTTP traffic is being processed correctly through the gateway
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2667 — 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-2011-2667 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