Security readout for executives and security teams
Plain-English summary
Older Logisim Evolution releases could be abused through a malicious circuit file. If a user opens that file, the XML parser may disclose local information and, on some system configurations, could lead to code execution. The source says this was fixed in 2.14.4.
Executive priority
Treat this as a targeted user-interaction risk, not an internet-wide emergency. Prioritize upgrade or removal where Logisim Evolution is used in education, labs, or engineering workflows that exchange circuit files.
Technical view
CVE-2018-1000889 is an XXE flaw in Logisim Evolution 2.14.3 and earlier, in circuit file loading through loadXmlFrom in src/com/cburch/logisim/file/XmlReader.java. The reported impact is information leak and possible RCE depending on system configuration.
Likely exposure
Exposure is limited to environments where Logisim Evolution 2.14.3 or earlier is installed and users open circuit files, especially files received from others. The provided sources do not identify packaged distributions, downstream forks, or automated processing scenarios.
Exploitation context
The cited description says exploitation requires a victim to open a specially crafted circuit file. The source bundle does not show CISA KEV listing, active exploitation, public exploit maturity, or observed campaign evidence.
Researcher notes
Evidence is narrow but clear: the vulnerable code path is named, affected versions are bounded, and the fix version is stated. Severity metadata, CVSS, CWE, and detailed patch mechanics are not included in the provided bundle.
Mitigation direction
- Upgrade Logisim Evolution to 2.14.4 or later.
- Do not open circuit files from untrusted or unknown sources.
- Remove unsupported older versions from managed endpoints.
- Check project or vendor guidance for any additional hardening advice.
Validation and detection
- Inventory endpoints for Logisim Evolution installations.
- Confirm installed versions are newer than 2.14.3.
- Review workflows where users exchange or download circuit files.
- Check whether security tooling flags risky XML parsing or suspicious file handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-1000889 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/reds-heig/logisim-evolution/pull/139CVE reference · x_refsource_MISC
- https://www.kvakil.me/posts/logisim/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.