{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-3141 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-3141 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-3141 is a high-severity vulnerability in n/a, published on 18 Mar 2021. 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-2021-3141 and fix it if it is affected.\n\nWhat it is: CVE-2021-3141 is a high-severity vulnerability in n/a, published on 18 Mar 2021. 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-2021-3141 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-2021-3141/ (Markdown: https://insights.sbomify.com/CVE-2021-3141/index.md)","id":"CVE-2021-3141","markdown":"https://insights.sbomify.com/CVE-2021-3141/index.md","name":"CVE-2021-3141","record":{"aliases":["GHSA-j6c5-5fqq-9mpv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Unisys Stealth","requires_auth":"low_privilege","summary":"A local attacker can recover the Keycloak password to access the Management Server and modify Stealth configuration.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"stealth","vendor":"unisys"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"In Unisys Stealth (core) before 6.0.025.0, the Keycloak password is stored in a recoverable format that might be accessible by a local attacker, who could gain access to the Management Server and change the Stealth configuration.","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-2021-3141","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"SaltStack Salt eauth tokens can be used once after expiration","id":"CVE-2021-3144"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2021-3139"},"products":["n/a"],"published":"2021-03-18","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-12053","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-24620","kev_date_added":null,"published":"2020-10-01"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2018-6592","kev_date_added":null,"published":"2018-02-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2024-23758","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.5,"headline":"TODO DODO","id":"CVE-2019-18193","kev_date_added":null,"published":"2020-02-03"},{"cvss_score":6.7,"headline":"Privilege escalation in n/a","id":"CVE-2021-35056","kev_date_added":null,"published":"2021-07-15"}],"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-03","vendors":["n/a"]},"summary":"A local attacker can recover the Keycloak password to access the Management Server and modify Stealth configuration.","url":"https://insights.sbomify.com/CVE-2021-3141/"}