{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3864 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3864 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3864 is a medium-severity vulnerability in Red Hat quay, published on 21 Jan 2020. 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-2019-3864 and fix it if it is affected.\n\nWhat it is: CVE-2019-3864 is a medium-severity vulnerability in Red Hat quay, published on 21 Jan 2020. 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-2019-3864 in the wild and no public exploit code.\n\nAffected product: Red Hat quay. 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-2019-3864/ (Markdown: https://insights.sbomify.com/CVE-2019-3864/index.md)","id":"CVE-2019-3864","markdown":"https://insights.sbomify.com/CVE-2019-3864/index.md","name":"CVE-2019-3864","record":{"aliases":["GHSA-rq69-788x-22hh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Quay container registry","requires_auth":"none","summary":"Attackers can exploit static CSRF tokens in Quay to perform actions on behalf of authenticated users, leading to account takeover.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quay","vendor":"redhat"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A vulnerability was discovered in all quay-2 versions before quay-3.0.0, in the Quay web GUI where POST requests include a specific parameter which is used as a CSRF token. The token is not refreshed for every request or when a user logged out and in again. An attacker could use a leaked token to gain access to the system using the user's account.","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":"Cross-site request forgery in quay","id":"CVE-2019-3864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in quay","id":"CVE-2019-3865"},"packages":[],"prev":{"headline":"Memory corruption in libssh2","id":"CVE-2019-3863"},"products":["quay"],"published":"2020-01-21","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.5,"headline":"Quay: cross-site request forgery (csrf) on config-editor page","id":"CVE-2023-4959","kev_date_added":null,"published":"2023-09-15"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Red Hat"]},"summary":"Attackers can exploit static CSRF tokens in Quay to perform actions on behalf of authenticated users, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2019-3864/"}