{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3867 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3867 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3867 is a medium-severity missing authorization vulnerability in quay, published on 18 Mar 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-3867 and fix it if it is affected.\n\nWhat it is: CVE-2019-3867 is a medium-severity missing authorization vulnerability in quay, published on 18 Mar 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-3867 in the wild and no public exploit code.\n\nAffected product: 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-3867/ (Markdown: https://insights.sbomify.com/CVE-2019-3867/index.md)","id":"CVE-2019-3867","markdown":"https://insights.sbomify.com/CVE-2019-3867/index.md","name":"CVE-2019-3867","record":{"aliases":["GHSA-pf92-7x8p-6x5m"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Container registry","requires_auth":"none","summary":"Attackers with stolen session tokens can control or delete user container repositories because Quay sessions never expire.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quay","vendor":"redhat"}],"cvss":{"score":4.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"A vulnerability was found in the Quay web application. Sessions in the Quay web application never expire. An attacker, able to gain access to a session, could use it to control or delete a user's container repository. Red Hat Quay 2 and 3 are vulnerable to this issue.","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":"Missing authorization in quay","id":"CVE-2019-3867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Keycloak","id":"CVE-2019-3868"},"packages":[],"prev":{"headline":"Information disclosure in openstack-mistral","id":"CVE-2019-3866"},"products":["quay"],"published":"2021-03-18","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":["n/a"]},"summary":"Attackers with stolen session tokens can control or delete user container repositories because Quay sessions never expire.","url":"https://insights.sbomify.com/CVE-2019-3867/"}