{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4910 exists.","fix":"No fix has been published for CVE-2023-4910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4910 is a medium-severity vulnerability in Red Hat 3scale API Management Platform 2, published on 6 Nov 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-4910 and fix it if it is affected.\n\nWhat it is: CVE-2023-4910 is a medium-severity vulnerability in Red Hat 3scale API Management Platform 2, published on 6 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4910 exists.\n\nAffected product: Red Hat 3scale API Management Platform 2. 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-4910/ (Markdown: https://insights.sbomify.com/CVE-2023-4910/index.md)","id":"CVE-2023-4910","markdown":"https://insights.sbomify.com/CVE-2023-4910/index.md","name":"CVE-2023-4910","record":{"aliases":["GHSA-g849-x577-8j36"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"3scale API Management","requires_auth":"low_privilege","summary":"Logged-out users can access personal API tokens via browser cache, exposing sensitive credentials to anyone with physical access to the device.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"3scale_api_management","vendor":"redhat"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"A flaw was found In 3Scale Admin Portal. If a user logs out from the personal tokens page and then presses the back button in the browser, the tokens page is rendered from the browser cache.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"3scale-admin-portal: logged out users tokens can be accessed","id":"CVE-2023-4910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"GNU C Library Buffer Overflow","id":"CVE-2023-4911"},"packages":[],"prev":{"headline":"Security feature bypass in Chrome","id":"CVE-2023-4909"},"products":["Red Hat 3scale API Management Platform 2"],"published":"2023-11-06","related":[{"cvss_score":8.8,"headline":"Cross-site scripting in 3scale-amp-system","id":"CVE-2022-1414","kev_date_added":null,"published":"2022-10-19"},{"cvss_score":7.5,"headline":"Auth bypass in Red Hat 3scale API Management Platform 2","id":"CVE-2024-10295","kev_date_added":null,"published":"2024-10-24"},{"cvss_score":7.5,"headline":"A flaw was found in 3scale’s APIcast gateway that enabled the TLS 1.0 protocol.","id":"CVE-2019-14852","kev_date_added":null,"published":"2021-03-18"},{"cvss_score":6.5,"headline":"Denial of service in 3scale/backend","id":"CVE-2021-20252","kev_date_added":null,"published":"2021-02-23"},{"cvss_score":6.3,"headline":"Missing authorization in Red Hat 3scale API Management","id":"CVE-2020-14388","kev_date_added":null,"published":"2021-06-02"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-20","vendors":["Red Hat"]},"summary":"Logged-out users can access personal API tokens via browser cache, exposing sensitive credentials to anyone with physical access to the device.","url":"https://insights.sbomify.com/CVE-2023-4910/"}