{"answers":{"affected":"1 open source package ship an affected version, including ejbca. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28942 in the wild and no public exploit code.","fix":"Upgrade ejbca to 7.4.3 or later.","what":"CVE-2020-28942 is a medium-severity missing authorization vulnerability in n/a, published on 19 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28942 and fix it if it is affected.\n\nWhat it is: CVE-2020-28942 is a medium-severity missing authorization vulnerability in n/a, published on 19 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-28942 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ejbca (Bitnami): affected all versions; fixed in 7.4.3\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-28942/ (Markdown: https://insights.sbomify.com/CVE-2020-28942/index.md)","id":"CVE-2020-28942","markdown":"https://insights.sbomify.com/CVE-2020-28942/index.md","name":"CVE-2020-28942","record":{"aliases":["BIT-ejbca-2020-28942","GHSA-vjxv-h84w-vj5j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EJBCA PKI server","requires_auth":"low_privilege","summary":"Attackers with valid client certificates can bypass RA restrictions in EJBCA EST enrollment, gaining unauthorized access to CA services.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ejbca","vendor":"primekey"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue exists in PrimeKey EJBCA before 7.4.3 when enrolling with EST while proxied through an RA over the Peers protocol. As a part of EJBCA's domain security model, the peer connector allows the restriction of client certificates (for the RA, not the end user) to a limited set of allowed CAs, thus restricting the accessibility of that RA to the rights it has within a specific role. While this works for other protocols such as CMP, it was found that the EJBCA enrollment over an EST implementation bypasses this check, allowing enrollment with a valid client certificate through any functioning and authenticated RA connected to the CA. NOTE: an attacker must already have a trusted client certificate and authorization to enroll against the targeted CA.","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":"Missing authorization in n/a","id":"CVE-2020-28942","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":1,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2020-28943"},"packages":[{"ecosystem":"Bitnami","fixed":["7.4.3"],"introduced":["0"],"last_affected":[],"package":"ejbca","purl":"pkg:bitnami/ejbca","source":"BIT-ejbca-2020-28942"}],"prev":{"headline":"Use after free in n/a","id":"CVE-2020-28941"},"products":["n/a"],"published":"2020-11-19","related":[{"cvss_score":9.8,"headline":"Business logic in n/a","id":"CVE-2022-34831","kev_date_added":null,"published":"2022-09-14"},{"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-04","vendors":["n/a"]},"summary":"Attackers with valid client certificates can bypass RA restrictions in EJBCA EST enrollment, gaining unauthorized access to CA services.","url":"https://insights.sbomify.com/CVE-2020-28942/"}