{"answers":{"affected":"2 open source packages ship an affected version, including io.apiman:apiman-manager-api-rest-impl. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-28640 in the wild and no public exploit code.","fix":"Upgrade io.apiman:apiman-manager-api-rest-impl to 3.1.0.Final or later.","what":"CVE-2023-28640 is a medium-severity missing authorization vulnerability in apiman, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-28640 and fix it if it is affected.\n\nWhat it is: CVE-2023-28640 is a medium-severity missing authorization vulnerability in apiman, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-28640 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.apiman:apiman-manager-api-rest-impl (Maven): affected all versions; fixed in 3.1.0.Final\n- io.apiman:apiman-manager-api-rest-impl (Maven): affected all versions; fixed in 3.1.0.Final\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-28640/ (Markdown: https://insights.sbomify.com/CVE-2023-28640/index.md)","id":"CVE-2023-28640","markdown":"https://insights.sbomify.com/CVE-2023-28640/index.md","name":"CVE-2023-28640","record":{"aliases":["GHSA-m6f8-hjrv-mw5f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"API Management Platform","requires_auth":"low_privilege","summary":"Authenticated attackers can access unauthorized API keys by guessing URLs, potentially allowing use of other users' resources without permission.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"apiman","vendor":"apiman"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Apiman is a flexible and open source API Management platform. Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.","ecosystems":["Maven"],"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":"Permissions bypass in Apiman could enable authenticated attacker to unpermitted API Key","id":"CVE-2023-28640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"AppArmor bypass with symlinked /proc in runc","id":"CVE-2023-28642"},"packages":[{"ecosystem":"Maven","fixed":["3.1.0.Final"],"introduced":["0"],"last_affected":[],"package":"io.apiman:apiman-manager-api-rest-impl","purl":null,"source":"GHSA-m6f8-hjrv-mw5f"},{"ecosystem":"Maven","fixed":["3.1.0.Final"],"introduced":["0"],"last_affected":[],"package":"io.apiman:apiman-manager-api-rest-impl","purl":"pkg:maven/io.apiman/apiman-manager-api-rest-impl","source":"GHSA-m6f8-hjrv-mw5f"}],"prev":{"headline":"GLPI vulnerable to reflected Cross-site Scripting in search pages","id":"CVE-2023-28639"},"products":["apiman"],"published":"2023-03-27","related":[{"cvss_score":6.5,"headline":"Apiman has potential permissions bypass","id":"CVE-2022-47551","kev_date_added":null,"published":"2022-12-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-02-19","vendors":["apiman"]},"summary":"Authenticated attackers can access unauthorized API keys by guessing URLs, potentially allowing use of other users' resources without permission.","url":"https://insights.sbomify.com/CVE-2023-28640/"}