CVE-2019-4750
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 · uneditedIBM Cloud App Management 2019.3.0 and 2019.4.0 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 173310.
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 confidenceIBM Cloud App Management versions 2019.3.0 and 2019.4.0 contains a cross-site request forgery (CSRF) vulnerability. An attacker could trick authenticated users into executing unwanted actions via malicious requests that the application trusts due to missing anti-CSRF protections.
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= 2019.3.0= 2019.4.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Cloud App Management versionLocate the installed version through the product admin console, about page, or installation logs. Look for version information in the product UI under Help > About or check the installation directory for version files.Affected if The installed version is exactly 2019.3.0 or 2019.4.0
-
Identify state-changing endpointsReview the application for forms, API endpoints, or URLs that perform actions such as creating, modifying, or deleting resources. Common areas include user management, configuration settings, data import/export, and administrative functions.Affected if The application has forms or APIs that handle user data or configuration changes
-
Inspect forms for anti-CSRF tokensView the HTML source of state-changing forms and check for hidden input fields containing anti-CSRF tokens. Also inspect API request payloads for token parameters or custom headers (such as X-CSRF-Token).Affected if Forms and API requests lack anti-CSRF token fields or custom headers
-
Verify Origin/Referer header validationSubmit a request with a mismatched or missing Origin/Referer header to a state-changing endpoint and observe if the application accepts or rejects it. This may require examining server logs or response codes.Affected if The application accepts requests without validating Origin or Referer headers
You are affected if the installed version is 2019.3.0 or 2019.4.0 and the application lacks anti-CSRF token protection on state-changing operations.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement anti-CSRF tokens for all state-changing operations (forms, API endpoints) and validate Origin/Referer headers. Alternatively, configure SameSite cookie attributes to prevent cross-origin requests.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4750 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-4750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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