Security readout for executives and security teams
Plain-English summary
IBM Cloud App Management versions 2019.3.0 and 2019.4.0 can expose stack traces from certain API requests. This may reveal implementation details useful to attackers, but the cited impact is limited to confidentiality and does not show direct system compromise.
Executive priority
Treat this as a moderate-priority information disclosure issue. It is not cited as actively exploited, but exposed management APIs can help attackers understand the environment and prepare follow-on attacks.
Technical view
CVE-2019-4751 is an information disclosure issue in IBM Cloud App Management APIs. The CVSS 3.0 vector is network-accessible, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, and no integrity or availability impact.
Likely exposure
Exposure is limited to environments running IBM Cloud App Management 2019.3.0 or 2019.4.0, especially where the affected APIs are reachable from untrusted networks.
Exploitation context
The source bundle does not cite active exploitation, and CISA KEV status is false. CVSS exploit maturity is listed as unproven. Attack value is mainly reconnaissance from leaked internal implementation details.
Researcher notes
The public details are sparse: no CWE is listed, affected versions are specific, and the description only states stack traces appear on certain API requests. Avoid assuming broader IBM products or undocumented exploitability.
Mitigation direction
- Identify any IBM Cloud App Management 2019.3.0 or 2019.4.0 deployments.
- Review IBM support guidance for the official remediation or fixed release path.
- Restrict API access to trusted networks and authenticated administrative paths where feasible.
- Monitor API error responses and logs for unexpected stack trace exposure.
Validation and detection
- Confirm deployed IBM Cloud App Management versions against the affected 2019.3.0 and 2019.4.0 releases.
- Review API error responses in a controlled environment for stack traces or implementation details.
- Check internet-facing and internal API exposure for affected Cloud App Management services.
- Document remediation status and remaining vendor-guidance dependencies.
Public sources used
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.
CVE-2019-4751 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
- 5.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AC:L/S:U/I:N/PR:N/AV:N/A:N/C:L/UI:N/RL:O/RC:C/E:U
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/AC:L/S:U/I:N/PR:N/AV:N/A:N/C:L/UI:N/RL:O/RC:C/E:U3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.3MediumVector: CVSS:3.0/AC:L/S:U/I:N/PR:N/AV:N/A:N/C:L/UI:N/RL:O/RC:C/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/6190557CVE reference · x_refsource_CONFIRM
- ibm-cam-cve20194751-info-disc (173311)CVE reference · vdb-entry, x_refsource_XF
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.
