dbcve.org
Sso Authentication LibraryApplication · Sap

CVE-2017-7696

HIGH · 7.5 CVSS v3.0 Published 2017-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
SAP AS JAVA SSO Authentication Library 2.0 through 3.0 allow remote attackers to cause a denial of service (memory consumption) via large values in the width and height parameters to otp_logon_ui_resources/qr, aka SAP Security Note 2389042.

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 SAP AS JAVA SSO Authentication Library 2.0-3.0 contains a Denial of Service vulnerability in the QR code generation endpoint (otp_logon_ui_resources/qr). The application fails to validate or restrict the width and height parameters, allowing attackers to request excessively large image dimensions that consume excessive server memory.

MitigationImplement strict input validation limiting maximum width and height values for QR code generation, and consider adding request rate limiting to prevent rapid repeated malicious requests.

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
Sso Authentication LibraryApplication
Affected:= 2.0= 3.0

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 SAP AS JAVA SSO Authentication Library version
    Locate the SAP AS JAVA installation directory and check the version of the SapSsoAuthLib or related SSO authentication library components. Common locations include /sapmnt/<SID>/sys/global or within the SAP AS JAVA lib directories. Use SAP maintenance tools or check manifest files for version information.
    Affected if The installed version is exactly 2.0 or exactly 3.0 of the SAP SSO Authentication Library
  2. Verify QR code endpoint exposure
    Check if the web application exposes the path /otp_logon_ui_resources/qr by reviewing web.xml deployment descriptors, URL mappings, or by attempting to access this endpoint from an internal network. Inspect the application's routing configuration for any paths starting with otp_logon_ui_resources.
    Affected if The endpoint /otp_logon_ui_resources/qr is accessible and responds to requests without authentication barriers
  3. Check for width/height parameter validation
    Review the application's input validation logic for the QR code generation functionality. Examine any servlet, controller, or filter code that handles the qr endpoint. Look for explicit checks that limit maximum values for width and height parameters.
    Affected if No validation exists or the validation allows width/height values exceeding reasonable image dimensions (e.g., above 1000 pixels)
  4. Inspect request configuration for rate limiting
    Review web application firewall settings, SAP ICM (Internet Communication Manager) configuration, or any proxy-layer rate limiting that may be applied to the QR code endpoint. Check if request size limits are configured.
    Affected if No rate limiting or request throttling is configured for the QR code generation endpoint

You are affected if the SAP AS JAVA SSO Authentication Library versions 2.0 or 3.0 are installed AND the /otp_logon_ui_resources/qr endpoint is accessible without proper input validation on width/height parameters.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation limiting maximum width and height values for QR code generation, and consider adding request rate limiting to prevent rapid repeated malicious requests.

Fix this in Sso Authentication Library Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7696 — 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-2017-7696 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