Security readout for executives and security teams
Plain-English summary
This CVE says Azkaban through 3.84.0 can process XML unsafely, creating an XXE risk. In business terms, affected Azkaban systems may expose sensitive local data or internal network interactions if an attacker can supply or influence relevant XML. The source bundle does not provide severity, CVSS, proof of exploitation, or a named fixed version.
Executive priority
Treat this as a targeted exposure review rather than an emergency based on current evidence. Prioritize environments running Azkaban through 3.84.0, especially where less-trusted users can submit jobs or manage XML-backed configuration.
Technical view
The issue is an XML External Entity vulnerability in Azkaban through 3.84.0, tied to validator/XmlValidatorManager.java and user/XmlUserManager.java. The available sources identify the weakness but do not include CVSS, CWE mapping, exploit prerequisites, patch details, or confirmed remediation steps.
Likely exposure
Exposure is most likely where Azkaban deployments at or below 3.84.0 allow users or administrators to upload, edit, import, or otherwise influence XML parsed by the named components. The bundle does not identify hosted services, default reachability, or authentication requirements.
Exploitation context
CISA KEV is false in the provided bundle, and no cited source states active exploitation. XXE issues can be serious, but this record lacks evidence about exploitability, access requirements, impact boundaries, or real-world attacks.
Researcher notes
The public record is sparse. Do not assume unauthenticated exploitation, data exfiltration scope, or a fixed release without upstream confirmation. Focus research on XML parser configuration and reachable XML input paths in the referenced Azkaban components.
Mitigation direction
- Inventory Azkaban deployments and identify any versions through 3.84.0.
- Check Azkaban issue 2478 and upstream guidance for confirmed fixes or safe upgrade paths.
- Restrict access to XML-related Azkaban administration or import workflows until remediated.
- Review custom Azkaban XML parsing changes for external entity handling.
- Monitor vendor release notes before asserting a specific fixed version.
Validation and detection
- Confirm the deployed Azkaban version for every environment.
- Identify whether XmlValidatorManager.java or XmlUserManager.java code paths are reachable.
- Review Azkaban roles that can submit or modify XML-backed configuration.
- Check application logs for unusual XML parser errors or unexpected resource access.
- Document whether compensating controls restrict untrusted XML input.
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.
CVE-2020-10992 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/azkaban/azkaban/issues/2478CVE 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.