LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35138: The MobileIron agents through 2021-03-22 for Android and iOS contain a hardcoded encryption key, used to en...

The MobileIron agents through 2021-03-22 for Android and iOS contain a hardcoded encryption key, used to encrypt the submission of username/password details during the authentication process, as demonstrated by Mobile@Work (aka com.mobileiron). The key is in the com/mobileiron/common/utils/C4928m.java file. NOTE: It has been asserted that there is no causality or connection between credential encryption and the MiTM attack

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-35138 concerns MobileIron Android and iOS agents that reportedly used a hardcoded key to protect username and password submissions. That design can reduce confidence in credential handling for affected mobile-management deployments. The public record also notes a dispute about connecting this issue to a man-in-the-middle attack.

Executive priority

Treat this as a credential-handling assurance issue for legacy MobileIron mobile agents, not as confirmed active exploitation. Prioritize inventory and agent upgrade decisions where MobileIron protected workforce device access or sensitive applications.

Technical view

The CVE describes MobileIron agents through 2021-03-22 for Android and iOS with a hardcoded encryption key in com/mobileiron/common/utils/C4928m.java, used during authentication credential submission. Public references include Optiv research, a GitHub project, and Ivanti’s response disputing some claims. No CVSS, CWE, CPE, or official fixed-version detail is provided in the bundle.

Likely exposure

Exposure is most likely in organizations that used MobileIron/Mobile@Work Android or iOS agents current on or before 2021-03-22. The CVE record does not provide CPEs or a precise affected-version matrix.

Exploitation context

The source bundle links public research and a GitHub project, so technical details were public. There is no KEV listing and no cited evidence of active exploitation. Ivanti disputed aspects of the Optiv research, including causality around a MiTM claim.

Researcher notes

Evidence is incomplete: CVSS, CWE, CPEs, and fixed-version metadata are absent. The CVE asserts a static key, while vendor commentary disputes broader conclusions. Validate claims against actual agent builds and vendor guidance before assigning exploitability or business impact.

Mitigation direction

  • Check Ivanti/MobileIron advisories for affected agent versions and fixed releases.
  • Upgrade or retire MobileIron agents released on or before 2021-03-22.
  • Review MDM authentication logs for unusual enumeration or failed-login patterns.
  • Enforce MFA and conditional access for managed-device authentication.
  • Limit legacy agent enrollment until vendor guidance is confirmed.

Validation and detection

  • Inventory Android and iOS devices running MobileIron or Mobile@Work agents.
  • Record installed agent versions and release dates for affected populations.
  • Confirm whether any device uses agents from 2021-03-22 or earlier.
  • Review vendor statements before treating MiTM impact as proven.
  • Check authentication telemetry for abnormal username enumeration indicators.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-35138 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.