CVE Intelligence
Skip to main content
MEDIUM

CVE-2019-11276

CVE-2019-11276 — Apps Manager sends tokens to Spring apps via HTTP

Pivotal 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.

Published Updated Sources: cvelistV5, pivotal

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

pivotal

pivotal_application_service_pas

CVSS base

5.4

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

pivotal

Products (1)

pivotal application service pas

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.4CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-319

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1056.004Input Capture: Credential API Hooking
  • T1040Network Sniffing

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /cloudapplication.

References

1 on the record

Elsewhere on this site

  • pivotalevery CVE for this vendor
  • CWE-319other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.