CVE-2019-10244
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 · uneditedIn Eclipse Kura versions up to 4.0.0, the Web UI package and component services, the Artemis simple Mqtt component and the emulator position service (not part of the device distribution) could potentially be target of XXE attack due to an improper factory and parser initialisation.
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 confidenceEclipse Kura versions up to 4.0.0 contain an XXE (XML External Entity) vulnerability in the Web UI package, component services, Artemis simple Mqtt component, and emulator position service. The XML parsers in these components are improperly initialized without disabling external entity processing, allowing attackers to inject malicious XML with external entity references to read local files or perform denial of service attacks.
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<= 4.0.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Eclipse Kura versionLocate the Kura installation directory and check the version file or manifest (commonly named about.html, version.properties, or META-INF/MANIFEST.MF in the Kura install root)Affected if Version is 4.0.0 or lower
-
Confirm Web UI is accessibleCheck if the Kura Web UI interface is enabled and accessible (typically on port 9443 or 8080, check webui configuration in conf/ directory)Affected if Web UI is enabled and Kura version is <= 4.0.0
-
Check if Artemis Mqtt component is activeReview deployed Kura bundles or configuration for 'org.eclipse.kura.core.certificate.CertificatesService' or similar Mqtt-related component configurationsAffected if Artemis simple Mqtt component is deployed and processes XML
-
Inspect XML parser configurationExamine XML parser initialization code or configuration files in the affected components (Web UI, component services, Artemis Mqtt, emulator position service) for absence of disallowing DTDs, external entities, and external document type declarationsAffected if XML parsers in affected components allow external entity processing
-
Verify emulator position service usageCheck if the emulator position service is configured or active in the Kura environmentAffected if Emulator position service is enabled and processes XML data
Environment is affected if Eclipse Kura version is 4.0.0 or lower and any of the affected components (Web UI, component services, Artemis Mqtt, or emulator position service) are in use with default XML parser settings that permit external entities.
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 dataSecure the XML parsers by disabling DTDs, external entities, and external document type declarations during parser factory initialization. Update to a patched version of Eclipse Kura if available, or manually harden parser configurations across all affected components.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10244 — 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-10244 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