{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-4427 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-4427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-4427 is a low-severity vulnerability in n/a, published on 19 May 2014. 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-2013-4427 and fix it if it is affected.\n\nWhat it is: CVE-2013-4427 is a low-severity vulnerability in n/a, published on 19 May 2014. 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-2013-4427 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-2013-4427/ (Markdown: https://insights.sbomify.com/CVE-2013-4427/index.md)","id":"CVE-2013-4427","markdown":"https://insights.sbomify.com/CVE-2013-4427/index.md","name":"CVE-2013-4427","record":{"aliases":["GHSA-ghjf-v3fm-fh8c"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux screen locker","requires_auth":"none","summary":"A local attacker can bypass the screen lock in pyxtrlock by exploiting unchecked return values in XCB functions, gaining unauthorized keyboard and mouse access.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"pyxtrlock","vendor":"leon_weber"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"pyxtrlock before 0.2 does not properly check the return values of the (1) xcb_grab_pointer and (2) xcb_grab_keyboard XCB library functions, which allows physically proximate attackers to gain access to the keyboard or mouse without unlocking the screen via unspecified vectors.","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":"Security feature bypass in n/a","id":"CVE-2013-4427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2013-4428"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2013-4426"},"products":["n/a"],"published":"2014-05-19","related":[{"cvss_score":3.6,"headline":"Auth bypass in n/a","id":"CVE-2013-4426","kev_date_added":null,"published":"2014-05-19"}],"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-06","vendors":["n/a"]},"summary":"A local attacker can bypass the screen lock in pyxtrlock by exploiting unchecked return values in XCB functions, gaining unauthorized keyboard and mouse access.","url":"https://insights.sbomify.com/CVE-2013-4427/"}