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

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

Is there a patch available for CVE-2013-1065?

Yes, a patch is available for CVE-2013-1065. Update the affected software to the latest version immediately.

Jockey CVE-2013-1065

MEDIUM

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

2013-10-03 security@ubuntu.com

Privilege Escalation Jockey Ubuntu Linux

4.6

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.6 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Oct 03, 2013 - 21:55 cve.org

MEDIUM 4.6

DescriptionCVE.org

backend.py in Jockey before 0.9.7-0ubuntu7.11 does not properly use D-Bus for communication with a polkit authority, which allows local users to bypass intended access restrictions by leveraging a PolkitUnixProcess PolkitSubject race condition via a (1) setuid process or (2) pkexec process, a related issue to CVE-2013-4288.

AnalysisAI

backend.py in Jockey before 0.9.7-0ubuntu7.11 does not properly use D-Bus for communication with a polkit authority, which allows local users to bypass intended access restrictions by leveraging a. Rated medium severity (CVSS 4.6), this vulnerability is low attack complexity.

Technical ContextAI

This vulnerability is classified under CWE-264. backend.py in Jockey before 0.9.7-0ubuntu7.11 does not properly use D-Bus for communication with a polkit authority, which allows local users to bypass intended access restrictions by leveraging a PolkitUnixProcess PolkitSubject race condition via a (1) setuid process or (2) pkexec process, a related issue to CVE-2013-4288. Affected products include: Martin Pitt Jockey, Canonical Ubuntu Linux. Version information: before 0.9.7.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.