Security readout for executives and security teams
Plain-English summary
Retrofit builds before the referenced fixing commit had an XXE issue in JAXB XML handling. If an affected application parsed attacker-controlled XML through that path, the impact could include server-side file disclosure or SSRF. The source bundle does not provide CVSS, affected version ranges, or evidence of active exploitation.
Executive priority
Treat this as dependency hygiene with potentially serious impact where untrusted XML is processed. Prioritize systems that accept XML from customers, partners, or public endpoints, but do not assume broad exposure without confirming JAXB usage.
Technical view
CVE-2018-1000844 describes an XML External Entity vulnerability in Square Open Source Retrofit before commit 4a693c5aeeef2be6c7ecf80e7b5ec79f6ab59437. The vulnerable area is JAXB processing. Reported outcomes are remote file reads and SSRF. The record says the issue was fixed after that commit.
Likely exposure
Exposure is likely limited to applications using vulnerable Retrofit code with JAXB/XML parsing reachable by untrusted XML input. The bundle does not identify package versions, CPEs, or specific releases, so teams must map dependencies to the fixing commit or vendor release notes.
Exploitation context
The source bundle does not cite public exploitation or KEV listing. The vulnerability class is externally triggerable when hostile XML reaches the affected JAXB path, but exploitation status and practical preconditions are not documented in the provided sources.
Researcher notes
The record lacks CVSS, CPEs, CWE mapping, and release-version detail. Focus analysis on commit ancestry, Retrofit JAXB converter usage, and trust boundaries around XML input. Do not claim active exploitation from the provided evidence.
Mitigation direction
- Upgrade Retrofit to a release containing commit 4a693c5aeeef2be6c7ecf80e7b5ec79f6ab59437 or later.
- Check Square Retrofit guidance for the packaged version that includes the fix.
- Reduce exposure by rejecting untrusted XML where JAXB parsing is unnecessary.
- Review XML parser settings for external entity and remote resource handling.
Validation and detection
- Inventory applications and lockfiles for Retrofit usage and XML/JAXB converters.
- Map installed Retrofit versions or commits against the fixing commit.
- Confirm untrusted XML cannot reach the affected JAXB parsing path.
- Verify patched builds are deployed in all runtime environments.
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.
Cloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-1000844 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/square/retrofit/pull/2735CVE 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.
