CVE-2020-15505
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 · uneditedA 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 that allows remote attackers to execute arbitrary code via unspecified vectors.
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 confidenceA pre-authentication remote code execution vulnerability in MobileIron Core, Connector, Sentry, and Monitor/Reporting Database (RDB) components. The vulnerability allows unauthenticated remote attackers to execute arbitrary code on affected systems via unspecified vectors. This was actively exploited in the wild targeting enterprise networks.
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< 10.3.0.4>= 10.4.0.0, < 10.4.0.4>= 10.5.1.0, < 10.5.1.1>= 10.5.2.0, < 10.5.2.1>= 10.6.0.0, < 10.6.0.1< 10.3.0.4>= 10.4.0.0, < 10.4.0.4>= 10.5.1.0, < 10.5.1.1>= 10.5.2.0, < 10.5.2.1>= 10.6.0.0, < 10.6.0.1< 2.0.0.2>= 9.7.0, < 9.7.3>= 9.8.0, < 9.8.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 MobileIron Core or Connector installationCheck for MobileIron Core or Connector by reviewing installed software listings, service entries, or consulting system documentation. Common installation paths include /opt/mobileiron or C:\Program Files\MobileIron. Look for Core or Connector-specific service processes.Affected if The product is installed and version falls within any of these ranges: < 10.3.0.4, >= 10.4.0.0 and < 10.4.0.4, >= 10.5.1.0 and < 10.5.1.1, >= 10.5.2.0 and < 10.5.2.1, or >= 10.6.0.0 and < 10.6.0.1
-
Identify MobileIron Sentry installationCheck for Sentry by reviewing installed software, service entries, or consulting system documentation. Look for Sentry-specific services or binaries. Common paths may be under /opt/mobileiron/sentry or similar.Affected if The product is installed and version falls within >= 9.7.0 and < 9.7.3, or >= 9.8.0 and < 9.8.1
-
Identify MobileIron RDB (Monitor And Reporting Database) installationCheck for Monitor and Reporting Database by reviewing installed software, database services, or consulting system documentation. This is typically a separate database component.Affected if The product is installed and version is < 2.0.0.2
If any MobileIron Core, Connector, Sentry, or RDB product is installed and its version matches the affected ranges listed above, the environment is vulnerable to remote code execution.
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.
dbcve · scoped2.0.0.29.7.39.8.1
Immediately upgrade affected MobileIron products to vendor-patched versions. For systems that cannot be patched, implement strict network segmentation and restrict external access to MobileIron interfaces as an interim control.
MobileIron Core/Connector: 10.3.0.4+, 10.4.0.4+, 10.5.1.1+, 10.5.2.1+ | RDB: 2.0.0.2+ | Sentry: 9.7.3+, 9.8.1+
- Identify which MobileIron product components are deployed in your environment (Core, Enterprise Connector, Monitor and Reporting Database, Sentry)
- For MobileIron Core and Enterprise Connector: Upgrade to version 10.3.0.4 or later, or 10.4.0.4 or later, or 10.5.1.1 or later, or 10.5.2.1 or later
- For Monitor and Reporting Database (RDB): Upgrade to version 2.0.0.2 or later
- For Sentry: Upgrade to version 9.7.3 or later, or 9.8.1 or later
- After upgrading, verify the fix by reviewing system logs for any exploitation attempts prior to patching
- Test the upgraded system in a non-production environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15505 — 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-2020-15505 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