dbcve.org
Access ManagerApplication · Netiq

CVE-2016-5757

CRITICAL · 9.8 CVSS v3.0 Published 2017-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
iManager Admin Console in NetIQ Access Manager 4.1 before 4.1.2 Hot Fix 1 and 4.2 before 4.2.2 was vulnerable to iFrame manipulation attacks, which could allow remote users to gain access to authentication credentials.

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 confidence

The iManager Admin Console in NetIQ Access Manager versions 4.1 before 4.1.2 Hot Fix 1 and 4.2 before 4.2.2 contains an iFrame manipulation vulnerability. Attackers can embed the authentication interface in a malicious iframe to perform clickjacking or frame injection attacks, allowing theft of admin credentials.

MitigationApply the vendor-supplied patches: update to NetIQ Access Manager 4.1.2 Hot Fix 1 or 4.2.2 as appropriate for your version.

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
Access ManagerApplication
Affected:= 4.1= 4.2

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NetIQ Access Manager version
    Check the installed version of NetIQ Access Manager by reviewing the product documentation, administration console, or version file. The version is typically displayed in the iManager login page or can be retrieved via the administration interface.
    Affected if The installed version is 4.1.x before 4.1.2 Hot Fix 1, or 4.2.x before 4.2.2.
  2. Confirm iManager Admin Console is accessible
    Verify that the iManager Admin Console web interface is exposed and accessible on the network. The vulnerability applies to the authentication interface served by iManager.
    Affected if iManager Admin Console is accessible via HTTP/HTTPS without additional access restrictions.
  3. Check for X-Frame-Options header
    Inspect the HTTP response headers returned by the iManager login page. Use browser developer tools or a tool like curl to fetch the login page and examine headers.
    Affected if The X-Frame-Options header is missing, set to ALLOWALL, or not configured to prevent framing.
  4. Review frame-ancestors CSP policy
    Examine the Content-Security-Policy header on the iManager authentication pages to see if frame-ancestors directive is properly configured.
    Affected if No frame-ancestors CSP directive is present, or it allows framing from untrusted sources.

A user is affected if NetIQ Access Manager version is 4.1 before 4.1.2 Hot Fix 1 or 4.2 before 4.2.2, and the iManager Admin Console lacks proper X-Frame-Options or CSP frame-ancestors protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches: update to NetIQ Access Manager 4.1.2 Hot Fix 1 or 4.2.2 as appropriate for your version.

Recommended fix High confidence

NetIQ Access Manager 4.1.2 Hot Fix 1 or 4.2.2

  1. Back up the current NetIQ Access Manager configuration and data
  2. Download NetIQ Access Manager 4.1.2 Hot Fix 1 or 4.2.2 from the Novell/NetIQ support portal
  3. Apply the hot fix or upgrade to the fixed version following NetIQ's standard installation procedures
  4. Verify the iManager Admin Console is accessible and functioning correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5757 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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