CVE-2019-11276
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 · uneditedPivotal Apps Manager, included in Pivotal Application Service versions 2.3.x prior to 2.3.16, 2.4.x prior to 2.4.12, 2.5.x prior to 2.5.8, and 2.6.x prior to 2.6.3, makes a request to the /cloudapplication endpoint via Spring actuator, and subsequent requests via unsecured http. An adjacent unauthenticated user could eavesdrop on the network traffic and gain access to the unencrypted token allowing the attacker to read the type of access a user has over an app. They may also modify the logging level, potentially leading to lost information that would otherwise have been logged.
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 confidencePivotal Apps Manager transmits authentication tokens to the /cloudapplication endpoint via Spring actuator over unencrypted HTTP. An adjacent unauthenticated attacker with network proximity can eavesdrop on this traffic to capture tokens, allowing them to view user access levels on applications. Attackers can also modify logging levels, potentially causing loss of audit information.
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>= 2.3.0, < 2.3.16>= 2.4.0, < 2.4.12>= 2.5.0, < 2.5.8>= 2.6.0, < 2.6.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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 Pivotal Application Service versionRun 'cf api' or check the installation manifest to determine the installed version of Pivotal Application ServiceAffected if The version falls within any of these ranges: 2.3.0-2.3.15, 2.4.0-2.4.11, 2.5.0-2.5.7, or 2.6.0-2.6.2
-
Verify Spring actuator endpoint exposureAccess the /cloudapplication actuator endpoint over HTTP (not HTTPS) and check if authentication tokens are transmitted in plain textAffected if The endpoint responds over HTTP and returns authentication tokens without encryption
-
Check network configuration for HTTP accessibilityInspect the Pivotal Application Service network configuration to determine whether the actuator endpoints are reachable over unencrypted HTTP from adjacent network segmentsAffected if Actuator endpoints are accessible over HTTP without TLS encryption from the network location in question
-
Confirm token transmission methodUse a network capture tool or inspect HTTP headers when accessing the /cloudapplication endpoint to verify if tokens appear in cleartextAffected if Authorization or authentication tokens are visible in plaintext within HTTP traffic
You are affected if Pivotal Application Service version is in the affected ranges AND the /cloudapplication Spring actuator endpoint is accessible over unencrypted HTTP, allowing adjacent attackers to capture authentication tokens.
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 data2.3.162.4.122.5.8
Upgrade Pivotal Application Service to version 2.3.16, 2.4.12, 2.5.8, 2.6.3 or later which enforces encrypted communication, or implement network-level protections such as VLAN segmentation and VPN access to prevent adjacent attackers from intercepting HTTP traffic.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11276 — 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-2019-11276 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