CVE-2017-14799
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 cross site scripting attack in handling the ESP login parameter handling in NetIQ Access Manager before 4.3.3 could be used to inject javascript code into the login page.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in NetIQ Access Manager's ESP (Enterprise Security Portal) login parameter handling before version 4.3.3 allows attackers to inject malicious JavaScript code into the login page via unsanitized user input.
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.3.3CVSS 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 installationLocate the NetIQ Access Manager installation directory, typically under /opt/novell/nam on Linux or C:\NetIQ\ on Windows, or check for NAM-related services running on the system.Affected if NetIQ Access Manager is installed and running on the system.
-
Determine the installed versionCheck the version of NetIQ Access Manager by inspecting version files in the installation directory, using the administration console, or running: namadmin -v or similar version command provided by the product.Affected if The installed version is lower than 4.3.3.
-
Verify ESP component is enabledConfirm that the Enterprise Security Portal (ESP) component is enabled and accessible. Check the NAM configuration for ESP-enabled endpoints, typically accessible via the /nidp or /nam endpoints.Affected if ESP is enabled and exposes login functionality.
-
Inspect login page parametersAccess the ESP login page (typically /nidp/ login endpoint) and examine how user input in parameters is handled. Submit a test parameter value with benign script tags to observe if input is reflected back unsanitized in the response.Affected if User-supplied input in login parameters is reflected in the response without proper encoding or sanitization.
The environment is affected if NetIQ Access Manager with ESP enabled is running a version lower than 4.3.3 and the login page reflects unsanitized user input.
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.3.3
Upgrade NetIQ Access Manager to version 4.3.3 or later to resolve the XSS vulnerability in ESP login parameter handling.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14799 — 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-14799 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