Security readout for executives and security teams
Cloud Foundry foundations using CAPI-release before 1.79.0 could let a highly privileged authenticated user impersonate another foundation user under specific conditions. The attacker needs permission to create UAA clients and knowledge of the victim's email. This is not broadly unauthenticated, but it can undermine trust boundaries inside a Cloud Foundry environment. Exposure is likely limited to Cloud Foundry deployments running CAPI-release before 1.79.0 where non-fully-trusted users can create UAA clients. Internet reachability matters less than authenticated access and delegated client-management permissions. Prioritize remediation for shared or multi-tenant Cloud Foundry foundations, especially where application teams can manage UAA clients. Treat this as a contained but important privilege-escalation risk rather than an unauthenticated internet emergency. Mitigation focus: Upgrade Cloud Foundry CAPI-release to version 1.79.0 or later.; Review the Cloud Foundry advisory for vendor-specific remediation guidance.; Restrict UAA client creation to trusted administrators only..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-3798 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:H0.55.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
6MediumVector: CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cloudfoundry.org/blog/cve-2019-3798CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.