CVE-2020-35138

Impact

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

Affected products

Weakness classification

References

• NVD record
• CVE.org record
• https://github.com/optiv/rustyIron
• https://play.google.com/store/apps/details?id=com.mobileiron&hl=en_US&gl=US
• https://www.ivanti.com/blog/a-warranted-response-to-inaccurate-optiv-research
• https://www.optiv.com/explore-optiv-insights/source-zero/mobileiron-mdm-contains-static-key-allowing-account-enumeration
• https://www.optiv.com/insights/source-zero/blog/mobileiron-mdm-contains-static-key-allowing-account-enumeration
• https://github.com/optiv/rustyIron
• https://play.google.com/store/apps/details?id=com.mobileiron&hl=en_US&gl=US
• https://www.ivanti.com/blog/a-warranted-response-to-inaccurate-optiv-research
• https://www.optiv.com/explore-optiv-insights/source-zero/mobileiron-mdm-contains-static-key-allowing-account-enumeration
• https://www.optiv.com/insights/source-zero/blog/mobileiron-mdm-contains-static-key-allowing-account-enumeration