Secure Access Control SystemApplication · Cisco
CVE-2014-8029
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 · uneditedOpen redirect vulnerability in the web interface in Cisco Secure Access Control System (ACS) allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via an unspecified parameter, aka Bug ID CSCuq74150.
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 confidenceOpen redirect vulnerability in Cisco Secure Access Control System (ACS) web interface allows remote attackers to craft malicious URLs that redirect users to arbitrary external websites for phishing purposes via an unspecified parameter in the web interface.
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
Secure Access Control SystemApplication
all versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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 Cisco ACS web interface is accessibleIdentify if the Cisco Secure Access Control System web interface is running. Check for HTTPS/HTTP services on typical ACS ports (443, 8443) or review network scans to determine if the ACS admin portal is reachable.Affected if The Cisco ACS web interface is exposed and reachable on the network
-
Identify the ACS versionLog into the ACS web interface and navigate to the System Administration > Operations Summary page, or use the CLI command 'show version' to confirm the installed version.Affected if Any version of Cisco Secure Access Control System is running (all versions are affected)
-
Inspect redirect parameters in URLsReview the ACS web application URLs for parameters that control redirection (such as 'url', 'redirect', 'target', or similar query parameters). Attempt to modify these parameters to point to an external domain and observe if the application allows the redirect.Affected if The application accepts and follows redirects to arbitrary external domains via URL parameters without validation
-
Check for external redirect responsesUsing a browser or HTTP tool, access the ACS login page and append a suspicious parameter value (such as '?redirect=http://example.com') to the URL. Observe whether the application returns a redirect (HTTP 302/301) to the untrusted domain.Affected if The ACS web interface returns HTTP redirects to domains outside the organization's control
-
Assess network exposure of the ACS web interfaceDetermine if the ACS web interface is accessible from untrusted networks (such as the internet) versus only from trusted internal networks. Review firewall rules and access control lists.Affected if The ACS web interface is accessible from untrusted networks and permits external redirect parameters
Your environment is affected if the Cisco ACS web interface is running and permits external URL redirects through its parameters without validation, regardless of version.
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 dataApply the vendor patch for bug CSCuq74150 when available; implement strict URL validation on redirect parameters to ensure only trusted destinations are allowed.
Fix this in Secure Access Control System
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8029 — 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-2014-8029 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