Application ServiceApplication · Pivotal Software

CVE-2019-3793

CRITICAL · 9.8 CVSS v3.1 Published 2019-04-24
Fix available
A fix is available. Upgrade to 665.0.28 / 666.0.21 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 Apps Manager Release, versions 665.0.x prior to 665.0.28, versions 666.0.x prior to 666.0.21, versions 667.0.x prior to 667.0.7, contain an invitation service that accepts HTTP. A remote unauthenticated user could listen to network traffic and gain access to the authorization credentials used to make the invitation requests.

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 Pivotal Apps Manager invitation service accepts requests over unencrypted HTTP rather than HTTPS, allowing remote unauthenticated attackers on the same network segment to intercept authorization credentials by sniffing network traffic.

MitigationUpgrade to patched versions (665.0.28+, 666.0.21+, 667.0.7+) or configure the invitation service to reject HTTP and only accept HTTPS connections.

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:>= 665.0.0, < 665.0.28>= 666.0.0, < 666.0.21>= 667.0.0, < 667.0.7

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.1/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. Identify the Pivotal Application Service version
    Locate the installation directory or deployment manifest for Pivotal Application Service and retrieve the exact version number installed in your environment
    Affected if The installed version falls within 665.0.0 to 665.0.27, 666.0.0 to 666.0.20, or 667.0.0 to 667.0.6
  2. Locate the Apps Manager invitation service
    Identify whether the Apps Manager component that handles user invitations is deployed and accessible in your environment
    Affected if The invitation service is present and operational in your deployment
  3. Verify if HTTP is enabled for the invitation service
    Check the network configuration or service binding for the invitation service to determine whether it listens on unencrypted HTTP (port 80)
    Affected if The invitation service accepts connections on HTTP port 80 instead of requiring HTTPS only
  4. Confirm network exposure
    Determine if the invitation service is accessible over the network rather than only on localhost or secured internal interfaces
    Affected if The HTTP endpoint for the invitation service is reachable from network segments accessible to untrusted users

You are affected if your Pivotal Application Service version is 665.0.0-665.0.27, 666.0.0-666.0.20, or 667.0.0-667.0.6 AND the Apps Manager invitation service accepts unencrypted HTTP connections accessible from your network.

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 665.0.28 / 666.0.21 / 667.0.7 or later
Fixed in 665.0.28666.0.21667.0.7
Interim mitigation

Upgrade to patched versions (665.0.28+, 666.0.21+, 667.0.7+) or configure the invitation service to reject HTTP and only accept HTTPS connections.

Recommended fix High confidence

665.0.28, 666.0.21, or 667.0.7 (depending on your current major version branch)

  1. Upgrade Pivotal Apps Manager to version 665.0.28 or later if running 665.0.x
  2. OR upgrade to version 666.0.21 or later if running 666.0.x
  3. OR upgrade to version 667.0.7 or later if running 667.0.x
  4. After upgrading, verify the invitation service is configured to use HTTPS only
  5. Confirm that network traffic to the invitation service is now encrypted

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

Fix this in Application Service Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3793 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