{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-5203 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-5203 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5203 is a vulnerability, published on 12 Jun 2024."},"fix_prompt":"Check this codebase for CVE-2024-5203 and fix it if it is affected.\n\nWhat it is: CVE-2024-5203 is a vulnerability, published on 12 Jun 2024. \nExploitation: There is no known exploitation of CVE-2024-5203 in the wild and no public exploit code.\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-2024-5203/ (Markdown: https://insights.sbomify.com/CVE-2024-5203/index.md)","id":"CVE-2024-5203","markdown":"https://insights.sbomify.com/CVE-2024-5203/index.md","name":"CVE-2024-5203","record":{"aliases":["GHSA-c9rq-mvr5-3w32"],"analysis":null,"analysis_generated_by":null,"assigner":"redhat","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"After careful review of CVE-2024-5203, it has been determined that the issue is not exploitable in real-world scenarios. Moreover, the exploit assumes that the attacker has access to a session code parameter that matches a cookie on the Keycloak server. However the attacker does not have access to the cookie, and can therefore not craft a malicious request.","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":"After careful review of CVE-2024-5203, it has been determined that the issue is not exploitable in real-world scenarios.","id":"CVE-2024-5203","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2024"},"n_packages":0,"n_references":0,"next":{"headline":"Swiss Toolkit For WP \u003c= 1.0.7 - Authenticated (Contributor+) Authentication Bypass","id":"CVE-2024-5204"},"packages":[],"prev":{"headline":"Dimensions RM - Arbitrary File Read","id":"CVE-2024-5202"},"products":[],"published":"2024-06-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2024-09-13","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2024-5203/"}