CVE-2021-21656: XML External Entity (XXE) Attacks in Jenkins Xcode Integration Plugin

Summary

18/03/2022
Yes i
High
7.1

CVE-2021-21656: XML external entity (XXE) attacks in Jenkins Xcode integration Plugin. Affects org.jenkins-ci.plugins:xcode-plugin versions < 2.0.15. Fixed in 2.0.15. 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 Penetration testing for web, API and mobile 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 Xcode Integration Plugin is a Maven package that provides integration between Jenkins and Xcode, allowing developers to build, test, and deploy iOS applications. It enables seamless automation of Xcode projects within Jenkins pipelines. However, versions 2.0.14 and earlier of the plugin are vulnerable to XML external entity (XXE) attacks.

Vulnerability Detail

The vulnerability in the Jenkins Xcode Integration Plugin arises from the lack of proper configuration of its XML parser, which leaves it susceptible to XML external entity (XXE) attacks. An attacker can exploit this vulnerability by submitting specially crafted XML input, which may lead to the disclosure of sensitive information, denial of service, or server-side request forgery (SSRF) attacks. The severity of this vulnerability is rated as HIGH with a CVSS score of 7.1.

How To Fix

Minimum fixed version

2.0.15

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 essential to update the Jenkins Xcode Integration Plugin to the fixed version to mitigate the risk of XML external entity (XXE) attacks.

Conclusion

The Jenkins Xcode Integration Plugin versions 2.0.14 and earlier are vulnerable to XML external entity (XXE) attacks. To ensure the security of the integration between Jenkins and Xcode, it is crucial to update the plugin to version 2.0.15 or later. This update includes the necessary configuration changes to prevent XXE attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:xcode-plugin →

Share this vulnerability

FAQ

The Jenkins Xcode Integration Plugin is a Maven package that enables the integration of Xcode projects with Jenkins, allowing developers to automate the build, test, and deployment processes of iOS applications.

An XML external entity (XXE) attack is a type of vulnerability that allows an attacker to exploit weakly configured XML parsers by injecting malicious XML input. This can lead to the disclosure of sensitive information, denial of service, or server-side request forgery (SSRF) attacks.

This vulnerability could result in the disclosure of sensitive information, such as files on the server, or enable denial of service attacks that could disrupt the availability of the Jenkins Xcode Integration Plugin. Additionally, it may facilitate server-side request forgery (SSRF) attacks, allowing an attacker to make requests to internal resources.

The severity of this vulnerability is rated as HIGH with a CVSS score of 7.1. It is crucial to address this vulnerability promptly to mitigate the risk of exploitation.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the pom.xml file, without requiring access to the code or installation.

How To Fix

Minimum fixed version

2.0.15

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