CVE-2019-4752
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 Emptoris Spend Analysis and IBM Emptoris Strategic Supply Management Platform 10.1.0.x, 10.1.1.x, and 10.1.3.x is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 173348.
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 confidenceSQL injection vulnerability in IBM Emptoris Spend Analysis and Strategic Supply Management Platform versions 10.1.0.x through 10.1.3.x allows remote attackers to execute arbitrary SQL statements via specially-crafted input, potentially enabling unauthorized view, add, modify, or delete operations on the back-end database.
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>= 10.1.0.0, < 10.1.0.34>= 10.1.1.0, < 10.1.1.33>= 10.1.3.0, < 10.1.3.29>= 10.1.0.0, < 10.1.0.34>= 10.1.1.0, < 10.1.1.33>= 10.1.3.0, < 10.1.3.29CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed IBM Emptoris product and versionLocate the application version information in the product's about page, version.info file, or administrative console. For IBM Emptoris Spend Analysis, check the application's system information or WAR file metadata. For Strategic Supply Management Platform, check the installed components listing in the administration interface.Affected if The installed version falls within these ranges: 10.1.0.0 through 10.1.0.33, 10.1.1.0 through 10.1.1.32, or 10.1.3.0 through 10.1.3.28.
-
Confirm the web application is remotely accessibleDetermine if the IBM Emptoris web interface is exposed to network access. Check the application server configuration (typically WebSphere or similar) for listening interfaces. Verify whether the application is reachable over HTTP/HTTPS from untrusted networks.Affected if The web interface is accessible from the internet or untrusted internal networks without additional authentication barriers.
-
Review HTTP access logs for SQL injection patternsExamine the application server access logs (typically found in the WebSphere logs directory or equivalent) for incoming requests containing SQL keywords such as UNION, SELECT, INSERT, DELETE, DROP, or common SQL injection payloads in query parameters, form inputs, or headers.Affected if Logs contain requests with SQL syntax or suspicious patterns in input fields that could indicate exploitation attempts.
-
Check for unauthorized database modificationsQuery the backend database (if accessible) for recent unexpected changes, such as new user accounts, modified permissions, or unexpected data entries in sensitive tables. Look at database audit logs for commands executed outside normal application workflows.Affected if Database contains unauthorized records, altered permissions, or audit logs show unexpected SQL commands executed from application user contexts.
You are affected if the installed IBM Emptoris version is 10.1.0.x before 10.1.0.34, 10.1.1.x before 10.1.1.33, or 10.1.3.x before 10.1.3.29, and the web interface is network-accessible.
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 data10.1.0.3410.1.1.3310.1.3.29
Apply vendor-provided patches for IBM Emptoris. As an immediate compensating control, implement strict input validation and restrict database account privileges to least privilege. Consider deploying a WAF to block SQL injection attempts until the patch can be applied.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4752 — 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-4752 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