{"answers":{"affected":"1 open source package ship an affected version, including ejbca. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34831 in the wild and no public exploit code.","fix":"Upgrade ejbca to 7.9.0 or later.","what":"CVE-2022-34831 is a critical vulnerability in n/a, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34831 and fix it if it is affected.\n\nWhat it is: CVE-2022-34831 is a critical vulnerability in n/a, published on 14 Sep 2022. 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-2022-34831 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ejbca (Bitnami): affected all versions; fixed in 7.9.0\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-2022-34831/ (Markdown: https://insights.sbomify.com/CVE-2022-34831/index.md)","id":"CVE-2022-34831","markdown":"https://insights.sbomify.com/CVE-2022-34831/index.md","name":"CVE-2022-34831","record":{"aliases":["BIT-ejbca-2022-34831","GHSA-w496-q2jp-3qx5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EJBCA PKI software","requires_auth":"none","summary":"Attackers can bypass ACME validation to issue certificates with unverified DNS names, undermining PKI trust integrity.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ejbca","vendor":"primekey"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered in Keyfactor PrimeKey EJBCA before 7.9.0, related to possible inconsistencies in DNS identifiers submitted in an ACME order and the corresponding CSR submitted during finalization. During the ACME enrollment process, an order is submitted containing an identifier for one or multiple dnsNames. These are validated properly in the ACME challenge. However, if the validation passes, a non-compliant client can include additional dnsNames the CSR sent to the finalize endpoint, resulting in EJBCA issuing a certificate including the identifiers that were not validated. This occurs even if the certificate profile is configured to not allow a DN override by the CSR.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Business logic in n/a","id":"CVE-2022-34831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":1,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2022-34832"},"packages":[{"ecosystem":"Bitnami","fixed":["7.9.0"],"introduced":["0"],"last_affected":[],"package":"ejbca","purl":"pkg:bitnami/ejbca","source":"BIT-ejbca-2022-34831"}],"prev":{"headline":"Use after free in n/a","id":"CVE-2022-34830"},"products":["n/a"],"published":"2022-09-14","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2020-11630","kev_date_added":null,"published":"2020-04-07"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-11627","kev_date_added":null,"published":"2020-04-07"},{"cvss_score":7.3,"headline":"Security feature bypass in n/a","id":"CVE-2020-25276","kev_date_added":null,"published":"2020-09-11"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2020-11629","kev_date_added":null,"published":"2020-04-07"},{"cvss_score":6.5,"headline":"Privilege escalation in n/a","id":"CVE-2020-11631","kev_date_added":null,"published":"2020-04-07"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-11626","kev_date_added":null,"published":"2020-04-07"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"Attackers can bypass ACME validation to issue certificates with unverified DNS names, undermining PKI trust integrity.","url":"https://insights.sbomify.com/CVE-2022-34831/"}