What is the CVSS score of CVE-2013-2190?

CVE-2013-2190 has a CVSS 2.0 base score of 2.1 (Low). CVSS vector: AV:L/AC:L/Au:N/C:P/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2013-2190?

Yes, a public proof-of-concept exploit is available for CVE-2013-2190. Prioritise patching immediately. EPSS: 0.1%.

Clutter CVE-2013-2190

LOW

Permissions, Privileges, and Access Controls (CWE-264)

2013-10-17 secalert@redhat.com

Privilege Escalation Clutter Opensuse

2.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

AV:L/AC:L/Au:N/C:P/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:L/AC:L/Au:N/C:P/I:N/A:N

Attack Vector

Local

Attack Complexity

Low

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Oct 17, 2013 - 23:55 cve.org

LOW 2.1

DescriptionCVE.org

The translate_hierarchy_event function in x11/clutter-device-manager-xi2.c in Clutter, when resuming the system, does not properly handle XIQueryDevice errors when a device has "disappeared," which causes the gnome-shell to crash and allows physically proximate attackers to access the previous gnome-shell session via unspecified vectors.

AnalysisAI

The translate_hierarchy_event function in x11/clutter-device-manager-xi2.c in Clutter, when resuming the system, does not properly handle XIQueryDevice errors when a device has "disappeared," which. Rated low severity (CVSS 2.1), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-264. The translate_hierarchy_event function in x11/clutter-device-manager-xi2.c in Clutter, when resuming the system, does not properly handle XIQueryDevice errors when a device has "disappeared," which causes the gnome-shell to crash and allows physically proximate attackers to access the previous gnome-shell session via unspecified vectors. Affected products include: Clutter Project Clutter, Opensuse.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.