dbcve.org
Icewall Sso AgentApplication · Hp

CVE-2019-11989

MEDIUM · 5.9 CVSS v3.0 Published 2019-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
A security vulnerability in HPE IceWall SSO Agent Option and IceWall MFA (Agent module ) could be exploited remotely to cause a denial of service. The versions and platforms of Agent Option modules that are impacted are as follows: 10.0 for Apache 2.2 on RHEL 5 and 6, 10.0 for Apache 2.4 on RHEL 7, 10.0 for Apache 2.4 on HP-UX 11i v3, 10.0 for IIS on Windows, 11.0 for Apache 2.4 on RHEL 7, MFA Proxy 4.0 (Agent module only) for Apache 2.4 on RHEL 7.

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 · moderate confidence

A denial of service vulnerability exists in HPE IceWall SSO Agent Option and IceWall MFA Agent modules. The vulnerability can be triggered remotely, causing the affected web server (Apache or IIS) to become unresponsive, likely through malformed request handling in the authentication agent.

MitigationApply available patches or updates from HPE for the specific IceWall SSO Agent version and platform in use. If no patch is available, consider implementing rate limiting or web application firewall rules to mitigate DoS attempts.

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
Icewall Sso AgentApplication
Affected:= 10.0= 11.0
Mfa ProxyApplication
Affected:= 4.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/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 HPE IceWall SSO Agent installation
    Locate the HPE IceWall SSO Agent installation directory or check installed programs on the server. Common locations include /opt/hp/icewall or C:\Program Files\HPE\IceWall on Windows. Use commands like 'ls' or check the Windows registry for installed software.
    Affected if HPE IceWall SSO Agent version 10.0 or 11.0 is found installed on the system
  2. Identify HPE MFA Proxy installation
    Locate the HPE MFA Proxy installation directory or check installed programs. Use system inventory tools or check for MFA Proxy-specific directories and binaries.
    Affected if HPE MFA Proxy version 4.0 is found installed on the system
  3. Verify installed versions
    Check the version of the installed IceWall SSO Agent or MFA Proxy using product-specific commands, configuration files, or version information displayed by the software. Compare against the affected versions: IceWall SSO Agent = 10.0 or = 11.0, MFA Proxy = 4.0.
    Affected if The installed version exactly matches 10.0 or 11.0 for IceWall SSO Agent, or 4.0 for MFA Proxy
  4. Confirm affected module is enabled
    Check if the IceWall SSO Agent module is loaded and active in the web server configuration (Apache httpd.conf or IIS configuration). Verify the authentication agent is handling requests by reviewing web server logs and active module status.
    Affected if The IceWall SSO Agent or MFA Proxy module is actively loaded and processing authentication requests on Apache or IIS

A system is affected if HPE IceWall SSO Agent version 10.0 or 11.0, or HPE MFA Proxy version 4.0 is installed with the authentication agent module enabled and handling web server requests.

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

Apply available patches or updates from HPE for the specific IceWall SSO Agent version and platform in use. If no patch is available, consider implementing rate limiting or web application firewall rules to mitigate DoS attempts.

Fix this in Icewall Sso Agent 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-2019-11989 — 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-2019-11989 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