What is the CVSS score of CVE-2014-2068?

CVE-2014-2068 has a CVSS 2.0 base score of 3.5 (Low). CVSS vector: AV:N/AC:M/Au:S/C:P/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a patch available for CVE-2014-2068?

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

Java CVE-2014-2068

LOW

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

2014-10-17 security@debian.org

Jenkins Privilege Escalation Java

3.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

3.5 LOW

AV:N/AC:M/Au:S/C:P/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:P/I:N/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Oct 17, 2014 - 15:55 cve.org

LOW 3.5

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

11 maven packages depend on org.jenkins-ci.main:jenkins-core (10 direct, 1 indirect)

Ecosystem-wide dependent count for version 1.533.

DescriptionCVE.org

The doIndex function in hudson/util/RemotingDiagnostics.java in CloudBees Jenkins before 1.551 and LTS before 1.532.2 allows remote authenticated users with the ADMINISTER permission to obtain sensitive information via vectors related to heapDump.

AnalysisAI

The doIndex function in hudson/util/RemotingDiagnostics.java in CloudBees Jenkins before 1.551 and LTS before 1.532.2 allows remote authenticated users with the ADMINISTER permission to obtain. Rated low severity (CVSS 3.5), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified under CWE-264. The doIndex function in hudson/util/RemotingDiagnostics.java in CloudBees Jenkins before 1.551 and LTS before 1.532.2 allows remote authenticated users with the ADMINISTER permission to obtain sensitive information via vectors related to heapDump. Affected products include: Jenkins. Version information: before 1.551.

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.