{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27831 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-27831 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27831 is a medium-severity missing authorization vulnerability in quay, published on 26 May 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27831 and fix it if it is affected.\n\nWhat it is: CVE-2020-27831 is a medium-severity missing authorization vulnerability in quay, published on 26 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-27831 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-2020-27831/ (Markdown: https://insights.sbomify.com/CVE-2020-27831/index.md)","id":"CVE-2020-27831","markdown":"https://insights.sbomify.com/CVE-2020-27831/index.md","name":"CVE-2020-27831","record":{"aliases":["GHSA-3mxm-3qx9-6gq2"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Container registry","requires_auth":"low_privilege","summary":"Attackers can add unauthorized email addresses to repository notifications due to improper authorization token protection in Red Hat Quay.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quay","vendor":"redhat"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"A flaw was found in Red Hat Quay, where it does not properly protect the authorization token when authorizing email addresses for repository email notifications. This flaw allows an attacker to add email addresses they do not own to repository notifications.","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-2020-27831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in quay","id":"CVE-2020-27832"},"packages":[],"prev":{"headline":"Null dereference in kernel","id":"CVE-2020-27830"},"products":["quay"],"published":"2021-05-26","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 can add unauthorized email addresses to repository notifications due to improper authorization token protection in Red Hat Quay.","url":"https://insights.sbomify.com/CVE-2020-27831/"}