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
References
Link | Resource |
---|---|
https://github.com/optiv/rustyIron | Exploit Third Party Advisory |
https://play.google.com/store/apps/details?id=com.mobileiron&hl=en_US&gl=US | Product Third Party Advisory |
https://www.ivanti.com/blog/a-warranted-response-to-inaccurate-optiv-research | Third Party Advisory |
https://www.optiv.com/explore-optiv-insights/source-zero/mobileiron-mdm-contains-static-key-allowing-account-enumeration | Exploit Third Party Advisory |
https://www.optiv.com/insights/source-zero/blog/mobileiron-mdm-contains-static-key-allowing-account-enumeration | Exploit Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2021-03-29 20:15
Updated : 2024-05-17 01:48
NVD link : CVE-2020-35138
Mitre link : CVE-2020-35138
CVE.ORG link : CVE-2020-35138
JSON object : View
Products Affected
mobileiron
- mobile\@work
CWE
CWE-798
Use of Hard-coded Credentials