{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27837 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-27837 is a medium-severity vulnerability in gdm, published on 28 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27837 and fix it if it is affected.\n\nWhat it is: CVE-2020-27837 is a medium-severity vulnerability in gdm, published on 28 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-27837 in the wild and no public exploit code.\n\nAffected product: gdm. 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-27837/ (Markdown: https://insights.sbomify.com/CVE-2020-27837/index.md)","id":"CVE-2020-27837","markdown":"https://insights.sbomify.com/CVE-2020-27837/index.md","name":"CVE-2020-27837","record":{"aliases":["DEBIAN-CVE-2020-27837","GHSA-xpm4-75c2-wrgc","OESA-2022-1811","OESA-2022-1812","UBUNTU-CVE-2020-27837"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"GDM display manager","requires_auth":"none","summary":"A race condition in GDM allows bypassing the lock screen for users with autologin enabled, granting unauthorized session access.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"gnome_display_manager","vendor":"gnome"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"A flaw was found in GDM in versions prior to 3.38.2.1. A race condition in the handling of session shutdown makes it possible to bypass the lock screen for a user that has autologin enabled, accessing their session without authentication. This is similar to CVE-2017-12164, but requires more difficult conditions to exploit.","ecosystems":[],"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":"Race condition in gdm","id":"CVE-2020-27837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Keycloak discloses information without authentication","id":"CVE-2020-27838"},"packages":[],"prev":{"headline":"Missing authorization in cluster-ingress-operator","id":"CVE-2020-27836"},"products":["gdm"],"published":"2020-12-28","related":[{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2018-14424","kev_date_added":null,"published":"2018-08-14"},{"cvss_score":7.2,"headline":"gdm3 would start gnome-initial-setup if it cannot contact accountservice","id":"CVE-2020-16125","kev_date_added":null,"published":"2020-11-10"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2013-4169","kev_date_added":null,"published":"2013-09-10"},{"cvss_score":4.1,"headline":"Auth bypass in gdm","id":"CVE-2017-12164","kev_date_added":null,"published":"2018-07-26"},{"cvss_score":2.1,"headline":"Denial of service in n/a","id":"CVE-2013-7273","kev_date_added":null,"published":"2014-04-29"},{"cvss_score":1.9,"headline":"Information disclosure in n/a","id":"CVE-2010-2387","kev_date_added":null,"published":"2012-12-21"}],"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":"A race condition in GDM allows bypassing the lock screen for users with autologin enabled, granting unauthorized session access.","url":"https://insights.sbomify.com/CVE-2020-27837/"}