CVE-2019-0283
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 · uneditedSAP NetWeaver Process Integration (Adapter Engine), fixed in versions 7.10 to 7.11, 7.30, 7.31, 7.40, 7.50; is vulnerable to Digital Signature Spoofing. It is possible to spoof XML signatures and send arbitrary requests to the server via PI Axis adapter. These requests will be accepted by the PI Axis adapter even if the payload has been altered, especially when the signed element is the body of the xml document.
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 confidenceSAP NetWeaver Process Integration Adapter Engine contains a digital signature spoofing vulnerability. The PI Axis adapter accepts XML signatures and processes requests even when the payload has been altered, specifically when the signed element is the body of the XML document. This allows attackers to spoof XML signatures and send arbitrary requests to the server.
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= 7.10= 7.11= 7.30= 7.31= 7.40= 7.50CVSS 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
- Low
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
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 SAP NetWeaver Process Integration versionCheck the installed SAP NetWeaver PI version via SAP transaction code SM51 or by reviewing the system information in the SAP NetWeaver Administrator. Compare the version number against the affected list: 7.10, 7.11, 7.30, 7.31, 7.40, or 7.50.Affected if The installed version matches exactly one of the affected versions listed.
-
Determine if PI Axis adapter is in useReview the integration scenario configurations in SAP NetWeaver Process Integration to identify if the PI Axis adapter (also known as Axis adapter) is deployed and active for any communication channels.Affected if The PI Axis adapter is configured and actively used for handling XML-based communications.
-
Check if XML signatures are used with the adapterExamine the communication channel configurations for the PI Axis adapter to determine whether XML digital signatures are enabled for message validation.Affected if XML digital signatures are configured for the PI Axis adapter communication channels.
-
Inspect XML signature validation settingsReview the adapter-specific security settings in the PI communication channel configuration to verify whether signature validation is properly enforced on the signed XML body element.Affected if XML signature validation is configured but allows altered message bodies to pass validation, or validation is not properly checking the signed body element integrity.
A system is affected if it runs SAP NetWeaver PI versions 7.10 through 7.50, uses the PI Axis adapter with XML digital signatures, and the signature validation does not properly verify the integrity of the signed XML body element.
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 dataApply SAP security patches for the affected versions (7.10-7.11, 7.30, 7.31, 7.40, 7.50) or upgrade to a patched release to remediate the digital signature validation weakness.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0283 — 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-0283 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