{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-49222 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49222 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49222 is a high-severity vulnerability in n/a, published on 7 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49222 and fix it if it is affected.\n\nWhat it is: CVE-2023-49222 is a high-severity vulnerability in n/a, published on 7 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-49222 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-2023-49222/ (Markdown: https://insights.sbomify.com/CVE-2023-49222/index.md)","id":"CVE-2023-49222","markdown":"https://insights.sbomify.com/CVE-2023-49222/index.md","name":"CVE-2023-49222","record":{"aliases":["GHSA-jvrv-28g9-r22f"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Precor touchscreen console","requires_auth":"none","summary":"A hardcoded private SSH key in Precor touchscreen consoles allows remote attackers to gain root privileges.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Precor touchscreen console P82 contains a private SSH key that corresponds to a default public key. A remote attacker could exploit this to gain root privileges.","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-2023-49222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-49223"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-49221"},"products":["n/a"],"published":"2024-06-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-13","vendors":["n/a"]},"summary":"A hardcoded private SSH key in Precor touchscreen consoles allows remote attackers to gain root privileges.","url":"https://insights.sbomify.com/CVE-2023-49222/"}