{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-42492 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-42492 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42492 is a high-severity vulnerability in v3.0.6433.1964, published on 25 Oct 2023. 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-42492 and fix it if it is affected.\n\nWhat it is: CVE-2023-42492 is a high-severity vulnerability in v3.0.6433.1964, published on 25 Oct 2023. 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-42492 in the wild and no public exploit code.\n\nAffected product: v3.0.6433.1964. 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-42492/ (Markdown: https://insights.sbomify.com/CVE-2023-42492/index.md)","id":"CVE-2023-42492","markdown":"https://insights.sbomify.com/CVE-2023-42492/index.md","name":"CVE-2023-42492","record":{"aliases":["GHSA-h7m9-mjxp-hhhv"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EisBaer SCADA","requires_auth":"low_privilege","summary":"EisBaer SCADA uses hard-coded cryptographic keys, allowing attackers to bypass security controls and access sensitive data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","cpe":[{"product":"eisbaer_scada","vendor":"busbaer"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"EisBaer Scada - CWE-321: Use of Hard-coded Cryptographic Key","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":"EisBaer Scada - CWE-321: Use of Hard-coded Cryptographic Key","id":"CVE-2023-42492","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":"EisBaer Scada - CWE-256: Plaintext Storage of a Password","id":"CVE-2023-42493"},"packages":[],"prev":{"headline":"EisBaer Scada - CWE-285: Improper Authorization","id":"CVE-2023-42491"},"products":["v3.0.6433.1964"],"published":"2023-10-25","related":[{"cvss_score":8.8,"headline":"EisBaer Scada - CWE-285: Improper Authorization","id":"CVE-2023-42491","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.5,"headline":"EisBaer Scada - CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')","id":"CVE-2023-42488","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.5,"headline":"EisBaer Scada - CWE-732: Incorrect Permission Assignment for Critical Resource","id":"CVE-2023-42489","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.5,"headline":"EisBaer Scada - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2023-42490","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.5,"headline":"EisBaer Scada - CWE-749: Exposed Dangerous Method or Function","id":"CVE-2023-42494","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.1,"headline":"EisBaer Scada - CWE-256: Plaintext Storage of a Password","id":"CVE-2023-42493","kev_date_added":null,"published":"2023-10-25"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-10","vendors":[" EisBaer Scada"]},"summary":"EisBaer SCADA uses hard-coded cryptographic keys, allowing attackers to bypass security controls and access sensitive data.","url":"https://insights.sbomify.com/CVE-2023-42492/"}