{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35137 is a high-severity vulnerability in n/a, published on 29 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35137 and fix it if it is affected.\n\nWhat it is: CVE-2020-35137 is a high-severity vulnerability in n/a, published on 29 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-35137 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-35137/ (Markdown: https://insights.sbomify.com/CVE-2020-35137/index.md)","id":"CVE-2020-35137","markdown":"https://insights.sbomify.com/CVE-2020-35137/index.md","name":"CVE-2020-35137","record":{"aliases":["GHSA-wrvw-xh7r-3r2g"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"MobileIron agent","requires_auth":"none","summary":"Hardcoded API key in MobileIron agents allows unauthorized access to SaaS discovery API, though the feature is opt-in and not enabled by default.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mobile\\@work","vendor":"mobileiron"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"The MobileIron agents through 2021-03-22 for Android and iOS contain a hardcoded API key, used to communicate with the MobileIron SaaS discovery API, as demonstrated by Mobile@Work (aka com.mobileiron). The key is in com/mobileiron/registration/RegisterActivity.java and can be used for api/v1/gateway/customers/servers requests. NOTE: Vendor states that this is an opt-in feature to the product - it is not enabled by default and customers cannot enable it without an explicit email to support. At this time, they do not plan change to make any changes to this feature.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35138"},"packages":[],"prev":{"headline":"Dolibarr authenticated Remote Code Execution","id":"CVE-2020-35136"},"products":["n/a"],"published":"2021-03-29","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35138","kev_date_added":null,"published":"2021-03-29"},{"cvss_score":5.4,"headline":"Weak cryptography in n/a","id":"CVE-2014-5903","kev_date_added":null,"published":"2014-09-15"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2021-3391","kev_date_added":null,"published":"2021-03-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Hardcoded API key in MobileIron agents allows unauthorized access to SaaS discovery API, though the feature is opt-in and not enabled by default.","url":"https://insights.sbomify.com/CVE-2020-35137/"}