CVE-2012-4982
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 assets/login on the Forescout CounterACT NAC device before 7.0 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the a parameter.
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 confidenceOpen redirect vulnerability in the Forescout CounterACT NAC device login page (assets/login) allows attackers to inject arbitrary URLs via the 'a' parameter, enabling phishing attacks by redirecting authenticated users to malicious websites.
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.3.4.10CVSS 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.
-
Identify Forescout CounterACT versionCheck the installed CounterACT version via the admin console or system information page, or use the command line tool provided by Forescout to query the appliance versionAffected if The installed version is exactly 6.3.4.10 (only this specific version is affected)
-
Confirm login page accessibilityAttempt to access the /assets/login endpoint on the CounterACT appliance (e.g., https://<device-ip>/assets/login)Affected if The login page is publicly or internally accessible without authentication restrictions
-
Test 'a' parameter for open redirectSubmit a login request with the 'a' parameter set to an external domain (e.g., /assets/login?a=http://malicious-site.com) and observe if the response performs an unvalidated redirectAffected if The application redirects to the URL specified in the 'a' parameter without validating it against an allowlist of trusted domains
-
Verify authenticated session behaviorAfter authenticating normally, access a URL with the 'a' parameter pointing to an external site and check if the appliance redirects the authenticated sessionAffected if Authenticated users are redirected to arbitrary external URLs based on the 'a' parameter value
You are affected if running CounterACT version 6.3.4.10 AND the /assets/login page with the 'a' parameter is accessible and performs unvalidated redirects to external URLs
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 dataUpgrade to Forescout CounterACT version 7.0 or later, or implement input validation on the 'a' parameter to restrict redirects to trusted domains only.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4982 — 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-2012-4982 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