{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4959 is a medium-severity vulnerability in Red Hat Quay 3, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-4959 and fix it if it is affected.\n\nWhat it is: CVE-2023-4959 is a medium-severity vulnerability in Red Hat Quay 3, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-4959 in the wild and no public exploit code.\n\nAffected product: Red Hat Quay 3. 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-4959/ (Markdown: https://insights.sbomify.com/CVE-2023-4959/index.md)","id":"CVE-2023-4959","markdown":"https://insights.sbomify.com/CVE-2023-4959/index.md","name":"CVE-2023-4959","record":{"aliases":["GHSA-xphq-2g8c-mfh6"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Container registry","requires_auth":"none","summary":"Attackers can force users to reconfigure the Quay instance, potentially adding admin users, via CSRF on the config-editor page.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quay","vendor":"redhat"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A flaw was found in Quay. Cross-site request forgery (CSRF) attacks force a user to perform unwanted actions in an application. During the pentest, it was detected that the config-editor page is vulnerable to CSRF. The config-editor page is used to configure the Quay instance. By coercing the victim’s browser into sending an attacker-controlled request from another domain, it is possible to reconfigure the Quay instance (including adding users with admin privileges).","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":"Quay: cross-site request forgery (csrf) on config-editor page","id":"CVE-2023-4959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"WCFM Marketplace \u003c= 3.6.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-4960"},"packages":[],"prev":{"headline":"Stackrox: missing http security headers allows for clickjacking in web ui","id":"CVE-2023-4958"},"products":["Red Hat Quay 3"],"published":"2023-09-15","related":[{"cvss_score":9,"headline":"Cross-site scripting in quay","id":"CVE-2020-27832","kev_date_added":null,"published":"2021-05-27"},{"cvss_score":6.5,"headline":"Quay: incorrect privilege assignment","id":"CVE-2025-4374","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":6.5,"headline":"Quay: clickjacking on config-editor page severity","id":"CVE-2023-4956","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":6,"headline":"Information disclosure in quay","id":"CVE-2019-10205","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":5.4,"headline":"Quay: red hat quay: authentication bypass allows privileged actions without valid credentials","id":"CVE-2026-6848","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":5.4,"headline":"Quay: stored cross site scripting","id":"CVE-2023-3384","kev_date_added":null,"published":"2023-07-24"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-07","vendors":["Red Hat"]},"summary":"Attackers can force users to reconfigure the Quay instance, potentially adding admin users, via CSRF on the config-editor page.","url":"https://insights.sbomify.com/CVE-2023-4959/"}