{"answers":{"affected":"4 open source packages ship an affected version, including io.quarkus:quarkus-oidc. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-1584 in the wild and no public exploit code.","fix":"Upgrade io.quarkus:quarkus-oidc to a fixed version for your release line: 2.13.0.Final or 3.1.0.Final.","what":"CVE-2023-1584 is a high-severity vulnerability in Red Hat RHINT Service Registry 2.5.4 GA, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-1584 and fix it if it is affected.\n\nWhat it is: CVE-2023-1584 is a high-severity vulnerability in Red Hat RHINT Service Registry 2.5.4 GA, published on 4 Oct 2023. 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-2023-1584 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.quarkus:quarkus-oidc (Maven): affected all versions; fixed in 2.13.0.Final\n- io.quarkus:quarkus-oidc (Maven): affected all versions; fixed in 2.13.0.Final\n- io.quarkus:quarkus-oidc (Maven): affected from 3.0.0; fixed in 3.1.0.Final\n- io.quarkus:quarkus-oidc (Maven): affected from 3.0.0; 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-1584/ (Markdown: https://insights.sbomify.com/CVE-2023-1584/index.md)","id":"CVE-2023-1584","markdown":"https://insights.sbomify.com/CVE-2023-1584/index.md","name":"CVE-2023-1584","record":{"aliases":["GHSA-6hc9-cf8x-hf83"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Quarkus OIDC extension","requires_auth":"none","summary":"Attackers can intercept ID and access tokens during authorization code flow if insecure HTTP is used, exposing sensitive user data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quarkus","vendor":"quarkus"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens.","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":"Quarkus-oidc: id and access tokens leak via the authorization code flow","id":"CVE-2023-1584","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":4,"n_references":6,"next":{"headline":"Race condition in AVG Antivirus","id":"CVE-2023-1585"},"packages":[{"ecosystem":"Maven","fixed":["2.13.0.Final"],"introduced":["0"],"last_affected":[],"package":"io.quarkus:quarkus-oidc","purl":null,"source":"GHSA-6hc9-cf8x-hf83"},{"ecosystem":"Maven","fixed":["2.13.0.Final"],"introduced":["0"],"last_affected":[],"package":"io.quarkus:quarkus-oidc","purl":"pkg:maven/io.quarkus/quarkus-oidc","source":"GHSA-6hc9-cf8x-hf83"},{"ecosystem":"Maven","fixed":["3.1.0.Final"],"introduced":["3.0.0"],"last_affected":[],"package":"io.quarkus:quarkus-oidc","purl":null,"source":"GHSA-6hc9-cf8x-hf83"},{"ecosystem":"Maven","fixed":["3.1.0.Final"],"introduced":["3.0.0"],"last_affected":[],"package":"io.quarkus:quarkus-oidc","purl":"pkg:maven/io.quarkus/quarkus-oidc","source":"GHSA-6hc9-cf8x-hf83"}],"prev":{"headline":"Null dereference in Linux kernel","id":"CVE-2023-1583"},"products":["RHINT Service Registry 2.5.4 GA","Red Hat build of Quarkus 2.13.8.Final"],"published":"2023-10-04","related":[{"cvss_score":9.8,"headline":"Code injection in quarkus dev ui config editor","id":"CVE-2022-4116","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":9.8,"headline":"Quarkus does not terminate HTTP requests header context","id":"CVE-2022-2466","kev_date_added":null,"published":"2022-08-31"},{"cvss_score":9.1,"headline":"Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass","id":"CVE-2024-12225","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":8.8,"headline":"Quarkus authorization bypass via semicolon path normalization inconsistency","id":"CVE-2026-39852","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.8,"headline":"Privilege escalation in quarkus","id":"CVE-2022-0981","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":8.6,"headline":"Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.","id":"CVE-2023-6267","kev_date_added":null,"published":"2024-01-25"},{"cvss_score":8.1,"headline":"Quarkus: http security policy bypass","id":"CVE-2023-4853","kev_date_added":null,"published":"2023-09-20"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Red Hat"]},"summary":"Attackers can intercept ID and access tokens during authorization code flow if insecure HTTP is used, exposing sensitive user data.","url":"https://insights.sbomify.com/CVE-2023-1584/"}