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

CVE-2014-2059 has a CVSS 2.0 base score of 6.5 (Medium). CVSS vector: AV:N/AC:L/Au:S/C:P/I:P/A:P. EPSS exploitation probability: 2.0%.

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

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

Jenkins CVE-2014-2059

MEDIUM

Path Traversal (CWE-22)

2014-03-01 security@debian.org

Path Traversal Jenkins

6.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Mar 01, 2014 - 00:01 cve.org

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

AnalysisAI

Directory traversal vulnerability in the CLI job creation (hudson/cli/CreateJobCommand.java) in Jenkins before 1.551 and LTS before 1.532.2 allows remote authenticated users to overwrite arbitrary. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. This Path Traversal vulnerability could allow attackers to access files and directories outside the intended path.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. Directory traversal vulnerability in the CLI job creation (hudson/cli/CreateJobCommand.java) in Jenkins before 1.551 and LTS before 1.532.2 allows remote authenticated users to overwrite arbitrary files via the job name. Affected products include: Jenkins. Version information: before 1.551.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.