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
07 Nov 2023, 03:21
Type | Values Removed | Values Added |
---|---|---|
Summary | 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 |
22 Apr 2022, 18:55
Type | Values Removed | Values Added |
---|---|---|
References |
|
04 Aug 2021, 19:15
Type | Values Removed | Values Added |
---|---|---|
Summary | ** DISPUTED ** 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. |
02 Apr 2021, 17:34
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : 5.0
v3 : 9.8 |
CPE | cpe:2.3:a:mobileiron:mobile\@work:*:*:*:*:*:android:*:* cpe:2.3:a:mobileiron:mobile\@work:*:*:*:*:*:iphone_os:*:* |
|
References | (MISC) https://www.optiv.com/explore-optiv-insights/source-zero/mobileiron-mdm-contains-static-key-allowing-account-enumeration - Exploit, Third Party Advisory | |
References | (MISC) https://play.google.com/store/apps/details?id=com.mobileiron&hl=en_US&gl=US - Product, Third Party Advisory | |
References | (MISC) https://github.com/optiv/rustyIron - Exploit, Third Party Advisory | |
CWE | CWE-798 |
30 Mar 2021, 18:15
Type | Values Removed | Values Added |
---|---|---|
Summary | 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. |
29 Mar 2021, 20:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2021-03-29 20:15
Updated : 2024-04-11 01:08
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