How severe is CVE-2013-0330?

CVE-2013-0330 has a CVSS 2.0 base score of 4.0, rated medium severity.

Is CVE-2013-0330 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2013-0330?

CVE-2013-0330 primarily affects Jenkins. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2013-0330?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2013-0330 published?

CVE-2013-0330 was published on 2013-03-19 and last updated on 2026-06-16.

CVE-2013-0330

CVE-2013-0330 is a medium-severity vulnerability in Jenkins with a CVSS 2.0 base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.0)
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jenkins
Published: 2013-03-19
Last modified: 2026-06-16

Description

Unspecified vulnerability in Jenkins before 1.502 and LTS before 1.480.3 allows remote authenticated users with write access to build arbitrary jobs via unknown attack vectors.

Frequently asked questions

What is CVE-2013-0330?: Unspecified vulnerability in Jenkins before 1.502 and LTS before 1.480.3 allows remote authenticated users with write access to build arbitrary jobs via unknown attack vectors.
How severe is CVE-2013-0330?: CVE-2013-0330 has a CVSS 2.0 base score of 4.0, rated medium severity.
Is CVE-2013-0330 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-0330?: CVE-2013-0330 primarily affects Jenkins. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2013-0330?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2013-0330 published?: CVE-2013-0330 was published on 2013-03-19 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:*
cpe:2.3:a:jenkins:jenkins:*:*:*:*:*:*:*:*

More vulnerabilities in Jenkins

CVE-2024-23897 — Critical (CVSS 9.8): Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces…
CVE-2021-21696 — Critical (CVSS 9.8): Jenkins 2.318 and earlier, LTS 2.303.2 and earlier does not limit agent read/write access to the libs/ directory inside…
CVE-2021-21694 — Critical (CVSS 9.8): FilePath#toURI, FilePath#hasSymlink, FilePath#absolutize, FilePath#isDescendant, and FilePath#get*DiskSpace do not…
CVE-2021-21693 — Critical (CVSS 9.8): When creating temporary files, agent-to-controller access to create those files is only checked after they've been…
CVE-2021-21692 — Critical (CVSS 9.8): FilePath#renameTo and FilePath#moveAllChildrenTo in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier only check…
CVE-2021-21691 — Critical (CVSS 9.8): Creating symbolic links is possible without the 'symlink' agent-to-controller access control permission in Jenkins…

All CVEs affecting Jenkins →