{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20681 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-20681 is a medium-severity vulnerability in n/a, published on 9 Jan 2019. 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-2018-20681 and fix it if it is affected.\n\nWhat it is: CVE-2018-20681 is a medium-severity vulnerability in n/a, published on 9 Jan 2019. 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-2018-20681 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-20681/ (Markdown: https://insights.sbomify.com/CVE-2018-20681/index.md)","id":"CVE-2018-20681","markdown":"https://insights.sbomify.com/CVE-2018-20681/index.md","name":"CVE-2018-20681","record":{"aliases":["DEBIAN-CVE-2018-20681","GHSA-wcwv-5qmw-xfpj","UBUNTU-CVE-2018-20681"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MATE Desktop Environment","requires_auth":"none","summary":"Physically proximate attackers can bypass the MATE screensaver lock by power-cycling external displays, revealing screen content and potentially executing applications.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mate-screensaver","vendor":"mate-desktop"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"mate-screensaver before 1.20.2 in MATE Desktop Environment allows physically proximate attackers to view screen content and possibly control applications. By unplugging and re-plugging or power-cycling external output devices (such as additionally attached graphical outputs via HDMI, VGA, DVI, etc.) the content of a screensaver-locked session can be revealed. In some scenarios, the attacker can execute applications, such as by clicking with a mouse.","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":"Security feature bypass in n/a","id":"CVE-2018-20681","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Fork CMS XSS Vulnerability","id":"CVE-2018-20682"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-20680"},"products":["n/a"],"published":"2019-01-09","related":[],"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-05","vendors":["n/a"]},"summary":"Physically proximate attackers can bypass the MATE screensaver lock by power-cycling external displays, revealing screen content and potentially executing applications.","url":"https://insights.sbomify.com/CVE-2018-20681/"}