CVE-2019-0267
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 Manufacturing Integration and Intelligence, versions 15.0, 15.1 and 15.2, (Illuminator Servlet) currently does not provide Anti-XSRF tokens. This might lead to XSRF attacks in case the data is being posted to the Servlet from an external application.
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 confidenceThe Illuminator Servlet in SAP Manufacturing Integration and Intelligence versions 15.0, 15.1, and 15.2 lacks Anti-XSRF (CSRF) token validation. This allows attackers to craft malicious requests that trick authenticated users into unknowingly submitting data to the servlet from external applications, potentially leading to unauthorized data manipulation.
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= 15.0= 15.1= 15.2CVSS 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.0/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 SAP MII installation and versionLocate the SAP MII installation directory and check the version file or launcher properties. Common paths include: /sap/mii/ or check the version.properties file in the installation root. Alternatively, access the SAP MII admin console and view the system information page.Affected if The installed version is exactly 15.0, 15.1, or 15.2.
-
Confirm Illuminator Servlet is enabledCheck the SAP MII web.xml configuration file (typically in the WEB-INF directory of the MII web application) for the Illuminator Servlet configuration. Look for a servlet definition with name 'Illuminator' or class com.sap.mii.IlluminatorServlet.Affected if The Illuminator Servlet is defined and enabled in the web.xml configuration.
-
Verify CSRF token validation is absentInspect the Illuminator Servlet Java class or configuration files for Anti-XSRF token validation logic. Search for terms like 'CSRF', 'XSRF', 'token', 'validateToken', or 'verifyToken' in the servlet source code or configuration. Check if state-changing operations (POST/PUT/DELETE) include token validation checks.Affected if No Anti-XSRF token validation logic is found in the Illuminator Servlet code or configuration, meaning requests lack CSRF protection.
If SAP MII versions 15.0, 15.1, or 15.2 are installed with the Illuminator Servlet enabled and no CSRF token validation is implemented, the environment is vulnerable to CVE-2019-0267.
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-XSRF token generation and validation on all state-changing operations (POST/PUT/DELETE) in the Illuminator Servlet to verify request authenticity.
- Consultation6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0267 — 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-0267 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