CVE-2017-7419
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 · uneditedA OAuth application in NetIQ Access Manager 4.3 before 4.3.2 and 4.2 before 4.2.4 allowed cross site scripting attacks due to unescaped "description" field that could be specified by the provider.
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 confidenceNetIQ Access Manager OAuth implementation does not properly sanitize/escape the 'description' field received from OAuth providers, allowing injection of malicious script content that executes in users' browsers when viewing OAuth configuration pages.
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>= 4.2, < 4.2.4>= 4.3, < 4.3.2CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 NetIQ Access Manager versionLocate the installed version of NetIQ Access Manager in the administration console or by checking the product documentation for version display locations. Common locations include the dashboard, about page, or system information section.Affected if The installed version is 4.2.0 through 4.2.3, or 4.3.0 through 4.3.1 (versions below 4.2.4 or 4.3.2 in the 4.2.x and 4.3.x branches)
-
Verify OAuth is configuredCheck whether OAuth identity provider connections are configured in the NetIQ Access Manager administration interface under the OAuth/OIDC provider settings.Affected if OAuth providers are configured and the description field contains unsanitized content from the OAuth provider response
-
Inspect OAuth configuration description fieldsExamine the OAuth provider configuration entries, specifically the description or display text fields that are populated from data received from the OAuth provider.Affected if The description field contains HTML, script tags, or JavaScript that was not escaped when rendered on the OAuth configuration pages
-
Review browser console for script errorsIf you have access to the OAuth configuration pages, view the page source or browser developer console while browsing the OAuth settings to check for any injected script execution.Affected if Arbitrary JavaScript executes in the browser when viewing OAuth configuration pages, indicating unsanitized content is being rendered
A user is affected if running NetIQ Access Manager versions 4.2.0-4.2.3 or 4.3.0-4.3.1 AND OAuth providers are configured with description fields that may contain unsanitized content from the OAuth provider.
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 data4.2.44.3.2
Upgrade NetIQ Access Manager to version 4.3.2 or 4.2.4 or later to obtain the patched code that properly escapes the description field content.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7419 — 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-2017-7419 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