EUVD-2013-4304

Malware in sbrugna...

EUVD-2013-4303

Malware in sbrugna...

EUVD-2019-2050

Malware in sbrugna...

CVE-2019-1010316

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...

CVE-2019-1010316

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...

CVE-2019-1010316

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...

Design/Logic Flaw

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...

CVE-2019-1010316

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...

CVE-2019-1010316

CVE-2019-1010316 affects pyxtrlock versions ≤ 0.3 and earlier. The issue is an Incorrect Access Control that yields a false locking impression when run in a non-X11 session. The fix is in version 0.4 . No exploitation details are provided in the connected documents.

CVE-2013-4427

pyxtrlock before 0.2 does not properly check the return values of the 1 xcbgrabpointer and 2 xcbgrabkeyboard XCB library functions, which allows physically proximate attackers to gain access to the keyboard or mouse without unlocking the screen via unspecified vectors...

CVE-2013-4426

pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to bypass the lock screen via multiple failed authentication attempts, which trigger a crash...

Design/Logic Flaw

pyxtrlock before 0.2 does not properly check the return values of the 1 xcbgrabpointer and 2 xcbgrabkeyboard XCB library functions, which allows physically proximate attackers to gain access to the keyboard or mouse without unlocking the screen via unspecified vectors...

Authentication flaw

pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to bypass the lock screen via multiple failed authentication attempts, which trigger a crash...

CVE-2013-4426

pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to bypass the lock screen via multiple failed authentication attempts, which trigger a crash...

CVE-2013-4426

Affected product: pyxtrlock prior to 0.1. The vulnerability arises from an incorrect variable name in the code, which allows physically proximate, local attackers to bypass the lock screen after multiple failed authentication attempts, ultimately triggering a crash. Exploitation details are not p...

CVE-2013-4427

CVE-2013-4427 affects pyxtrlock before 0.2. The vulnerability arises because the program does not properly check the return values of xcb_grab_pointer and xcb_grab_keyboard, allowing physically proximate attackers to gain access to the keyboard or mouse without unlocking the screen via unspecifie...