{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1010316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1010316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1010316 is a high-severity vulnerability in pyxtrlock, published on 11 Jul 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-2019-1010316 and fix it if it is affected.\n\nWhat it is: CVE-2019-1010316 is a high-severity vulnerability in pyxtrlock, published on 11 Jul 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-2019-1010316 in the wild and no public exploit code.\n\nAffected product: pyxtrlock. 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-1010316/ (Markdown: https://insights.sbomify.com/CVE-2019-1010316/index.md)","id":"CVE-2019-1010316","markdown":"https://insights.sbomify.com/CVE-2019-1010316/index.md","name":"CVE-2019-1010316","record":{"aliases":["GHSA-9vr4-wf8m-8m69"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux screen locker","requires_auth":"low_privilege","summary":"Attackers can bypass screen locking in non-X11 sessions, leaving the desktop accessible despite the lock indicator.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dwf","cpe":[{"product":"pyxtrlock","vendor":"pyxtrlock_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. The fixed version is: 0.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in pyxtrlock","id":"CVE-2019-1010316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in WavPack","id":"CVE-2019-1010317"},"packages":[],"prev":{"headline":"Denial of service in WavPack","id":"CVE-2019-1010315"},"products":["pyxtrlock"],"published":"2019-07-11","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":["pyxtrlock"]},"summary":"Attackers can bypass screen locking in non-X11 sessions, leaving the desktop accessible despite the lock indicator.","url":"https://insights.sbomify.com/CVE-2019-1010316/"}