{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11628 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11628 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11628 is a medium-severity vulnerability in n/a, published on 7 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11628 and fix it if it is affected.\n\nWhat it is: CVE-2020-11628 is a medium-severity vulnerability in n/a, published on 7 Apr 2020. 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-2020-11628 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-2020-11628/ (Markdown: https://insights.sbomify.com/CVE-2020-11628/index.md)","id":"CVE-2020-11628","markdown":"https://insights.sbomify.com/CVE-2020-11628/index.md","name":"CVE-2020-11628","record":{"aliases":["GHSA-jfrh-cwq3-hcj6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EJBCA PKI system","requires_auth":"none","summary":"Attackers can bypass remote protocol restrictions in EJBCA by modifying the URI string, allowing access to protocols that should be disabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ejbca","vendor":"primekey"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. It is intended to support restriction of available remote protocols (CMP, ACME, REST, etc.) through the system configuration. These restrictions can be bypassed by modifying the URI string from a client. (EJBCA's internal access control restrictions are still in place, and each respective protocol must be configured to allow for enrollment.)","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":"Security feature bypass in n/a","id":"CVE-2020-11628","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2020-11629"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-11627"},"products":["n/a"],"published":"2020-04-07","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":"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 can bypass remote protocol restrictions in EJBCA by modifying the URI string, allowing access to protocols that should be disabled.","url":"https://insights.sbomify.com/CVE-2020-11628/"}