dbcve.org
Application ServiceApplication · Pivotal Software

CVE-2019-3777

CRITICAL · 9.8 CVSS v3.0 Published 2019-03-07
Fix available
A fix is available. Upgrade to 2.2.12 / 2.3.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Pivotal Application Service (PAS), versions 2.2.x prior to 2.2.12, 2.3.x prior to 2.3.7 and 2.4.x prior to 2.4.3, contain apps manager that uses a cloud controller proxy that fails to verify SSL certs. A remote unauthenticated attacker that could hijack the Cloud Controller's DNS record could intercept access tokens sent to the Cloud Controller, giving the attacker access to the user's resources in the Cloud Controller

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 apps manager component in Pivotal Application Service contains a cloud controller proxy that fails to properly validate SSL certificates. This allows a remote unauthenticated attacker who hijacks the Cloud Controller's DNS record to intercept access tokens in transit, gaining unauthorized access to user resources within the Cloud Controller.

MitigationUpgrade Pivotal Application Service to version 2.2.12, 2.3.7, 2.4.3 or later to remediate the SSL certificate verification failure in the apps manager proxy.

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
Application ServiceApplication
Affected:>= 2.2.0, < 2.2.12>= 2.3.0, < 2.3.7>= 2.4.0, < 2.4.3

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Determine installed Pivotal Application Service version
    Run 'cf target' or check the Pivotal Operations Manager dashboard to find the PAS version currently deployed
    Affected if The version falls within >=2.2.0 and <2.2.12, >=2.3.0 and <2.3.7, or >=2.4.0 and <2.4.3
  2. Verify apps manager component is in use
    Check if the apps manager UI or API is accessible in your PAS environment by accessing the apps manager endpoint
    Affected if Apps manager is deployed and accessible in the environment
  3. Confirm Cloud Controller API endpoint configuration
    Run 'cf api' to see the Cloud Controller API endpoint URL configured for the environment
    Affected if A Cloud Controller API endpoint is configured and reachable
  4. Check SSL certificate validation settings for CC proxy
    Inspect the PAS deployment manifest or configuration for cloud_controller_proxy settings, specifically looking for ssl_verification_enabled or certificate_validation flags
    Affected if SSL certificate validation is disabled or not properly configured for the cloud controller proxy

Your environment is affected if you are running a PAS version in the affected ranges AND the apps manager cloud controller proxy is in use with SSL certificate validation not enforced.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.12 / 2.3.7 / 2.4.3 or later
Fixed in 2.2.122.3.72.4.3
Interim mitigation

Upgrade Pivotal Application Service to version 2.2.12, 2.3.7, 2.4.3 or later to remediate the SSL certificate verification failure in the apps manager proxy.

Recommended fix High confidence

2.2.12, 2.3.7, or 2.4.3 (depending on your current version branch)

  1. Identify current PAS version by checking the Apps Manager or using the cf CLI 'cf curl /v2/info' endpoint
  2. If running 2.2.x: upgrade to version 2.2.12 or later
  3. If running 2.3.x: upgrade to version 2.3.7 or later
  4. If running 2.4.x: upgrade to version 2.4.3 or later
  5. Follow Pivotal's standard upgrade procedures for PAS, including backing up the deployment
  6. After upgrade, verify SSL certificate validation is working by confirming the Cloud Controller proxy properly validates certificates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Application Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

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