dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2018-11469

MEDIUM · 5.9 CVSS v3.0 Published 2018-05-25
Fix available
A fix is available. Upgrade to after 1.8.9 or later.
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
Incorrect caching of responses to requests including an Authorization header in HAProxy 1.8.0 through 1.8.9 (if cache enabled) allows attackers to achieve information disclosure via an unauthenticated remote request, related to the proto_http.c check_request_for_cacheability function.

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

In HAProxy 1.8.0-1.8.9 with caching enabled, the check_request_for_cacheability function in proto_http.c incorrectly caches responses to requests containing an Authorization header. This allows unauthenticated attackers to obtain cached sensitive responses by making requests without credentials.

MitigationUpgrade HAProxy to version 1.8.10 or later, or disable caching if not required. If upgrade is not immediately possible, ensure no sensitive data is served through cached responses.

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
Ubuntu LinuxOperating system
Affected:= 18.04
HaproxyWeb server / proxy
Affected:>= 1.8.0, <= 1.8.9

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

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Check HAProxy version
    Run 'haproxy -v' or 'haproxy -vv' to display the installed version number
    Affected if The version displayed is >= 1.8.0 and <= 1.8.9
  2. Verify caching is enabled in configuration
    Inspect the HAProxy configuration file (typically /etc/haproxy/haproxy.cfg) and search for 'cache' directives or 'http-request' rules related to caching
    Affected if The configuration contains cache definitions or caching-related rules (e.g., 'http-request set-cache' or 'use-cache' statements)
  3. Confirm cache is used for responses
    Review the HAProxy configuration for 'http-response set-cache' or 'use-cache' rules that associate backends or responses with a cache store
    Affected if Cache rules are present that actually route traffic through the cache module

You are affected if HAProxy version is between 1.8.0 and 1.8.9 AND caching is enabled in your configuration

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
Upgrade available Upgrade to a release after 1.8.9
Interim mitigation

Upgrade HAProxy to version 1.8.10 or later, or disable caching if not required. If upgrade is not immediately possible, ensure no sensitive data is served through cached responses.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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