CVE-2018-1000012: XXE vulnerability in Jenkins Warnings Plugin

Summary

14/05/2022
Yes i
High
8.8

CVE-2018-1000012: XXE vulnerability Jenkins Warnings Plugin. Affects org.jvnet.hudson.plugins:warnings versions < 4.65. Fixed in 4.65. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Warnings Plugin is a Maven package that is used in the Jenkins build process. It provides functionality to parse files and extract warnings or issues. This plugin is commonly used in continuous integration and delivery pipelines to identify and report code quality issues. However, versions 4.64 and earlier of the plugin are vulnerable to an XML External Entity (XXE) attack.

Vulnerability Detail

The XXE vulnerability in the Jenkins Warnings Plugin allows attackers with user permissions in Jenkins to exploit XML external entities in the files parsed during the build process. This can lead to several security risks, including the extraction of sensitive information from the Jenkins master, server-side request forgery, or denial-of-service attacks. The vulnerability has a CVSS score of 8.8, indicating a high severity level.

How To Fix

Minimum fixed version

4.65

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to upgrade to the fixed version of the Jenkins Warnings Plugin to ensure the security of the Jenkins environment.

Conclusion

The XXE vulnerability in the Jenkins Warnings Plugin poses a significant security risk to Jenkins environments. It is crucial to upgrade to the fixed version of the plugin (4.65 or later) to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jvnet.hudson.plugins:warnings →

Share this vulnerability

FAQ

The Jenkins Warnings Plugin is a Maven package used in Jenkins to parse files and extract warnings or issues during the build process.

An XML External Entity (XXE) attack is a vulnerability that allows an attacker to exploit the processing of XML data and entities, potentially leading to information disclosure, server-side request forgery, or denial-of-service attacks.

The risks associated with this vulnerability include the extraction of sensitive information from the Jenkins master, server-side request forgery, or denial-of-service attacks.

The CVSS score of this vulnerability is 8.8, indicating a high severity level.

To fix this vulnerability, it is recommended to upgrade the Jenkins Warnings Plugin to version 4.65 or later.

Related vulnerabilities

Recent vulnerabilities recorded for org.jvnet.hudson.plugins:warnings.

How To Fix

Minimum fixed version

4.65

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback