CVE-2020-15505
Mobileiron Core ≤ 10.3.0.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2020-15505 is a critical-severity Use of Incorrectly-Resolved Name or Reference (CWE-706) vulnerability in Mobileiron Core. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2020-15505 is a remote code execution vulnerability affecting MobileIron Core and Connector versions 10.3.0.3 and earlier along with multiple 10.4.x, 10.5.x, and 10.6.0.0 releases; Sentry versions 9.7.2 and earlier plus 9.8.0; and Monitor and Reporting Database (RDB) version 2.0.0.1 and earlier. The flaw carries a CVSS score of 9.8 and is associated with CWE-706, enabling remote attackers to execute arbitrary code through unspecified vectors that reference materials indicate involve Hessian-based Java deserialization.
Unauthenticated attackers with network access can exploit the issue without user interaction to achieve full remote code execution on affected MobileIron components, potentially compromising device management, authentication, and reporting functions in enterprise mobile deployments.
MobileIron advisory information states that security updates are available to address the vulnerability in the listed products. Public references also include exploit code demonstrating the deserialization path, indicating active researcher interest shortly after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-7497
Vulnerability Data
A remote code execution vulnerability in MobileIron Core & Connector versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0; and Sentry versions 9.7.2 and earlier, and 9.8.0; and Monitor and Reporting Database (RDB) version 2.0.0.1 and earlier…
more
that allows remote attackers to execute arbitrary code via unspecified vectors.
- CWE(s)
- KEV Date Added
- 03 November 2021
Related Threats
Threat-Actor AttributionAI
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network segmentation and routing policies reduce the chance that a mis-resolved name leads to an unintended external resource.
Segregated networks limit the blast radius when a name or reference resolves outside the intended control sphere.
Secure SDLC practices include design reviews that can catch incorrect name or reference handling before deployment.
A.8.26 only requires that security requirements (including those that could address name-resolution issues) be identified during development or acquisition; it does not itself enforce, implement, or stop exploitation of an incorrectly-resolved name or reference.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, security-oriented design reviews, hardening) that reach many but not all name-resolution mistakes; a bounded remainder (e.g. flawed resolution logic inside trusted components or libraries) can still be introduced and exploited.
Secure-coding standards directly address canonicalization, input validation and safe name resolution, mitigating CWE-706.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-706, a class-level weakness, and none of its children carries one either.