CVE-2018-11788: XML External Entity Reference in Apache Karaf

Summary

07/01/2019
Yes i
Critical
9.8

CVE-2018-11788: XML External Entity Reference in Apache Karaf. Affects org.apache.karaf.specs:org.apache.karaf.specs.java.xml across 2 version ranges.

< 4.1.7 >= 4.2.0, < 4.2.2

Fixed in 4.1.7 or 4.2.2, depending on the release line you run. 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

Apache Karaf is an open-source OSGi-based runtime container for deploying and managing applications. It provides a features deployer that allows users to hot deploy a features XML file by placing it in the deploy folder. The features XML is parsed by the XMLInputFactory class. However, prior to versions 4.1.7 and 4.2.2, Apache Karaf did not include any mitigation codes against XML External Entity (XXE) attacks.

Vulnerability Detail

The absence of XXE mitigation in Apache Karaf versions prior to 4.1.7 and 4.2.2 poses a potential security risk. An attacker can exploit this vulnerability by injecting external XML entities, leading to various consequences such as information disclosure, denial of service, or server-side request forgery. This vulnerability has a CVSS score of 9.8, indicating its critical severity.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 4.1.7 4.1.7
  • >= 4.2.0, < 4.2.2 4.2.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to Apache Karaf version 4.1.7 or 4.2.2.

Conclusion

The XML External Entity Reference vulnerability in Apache Karaf versions prior to 4.1.7 and 4.2.2 can be mitigated by upgrading to the latest secure version. It is crucial to promptly apply the recommended fix to protect against potential exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.karaf.specs:org.apache.karaf.specs.java.xml →

Share this vulnerability

FAQ

Apache Karaf is an open-source OSGi-based runtime container for deploying and managing applications.

XML External Entity (XXE) is a vulnerability that allows an attacker to include external entities in an XML document, potentially leading to information disclosure, denial of service, or server-side request forgery.

The consequences of this vulnerability can include information disclosure, denial of service, or server-side request forgery, depending on how it is exploited.

The CVSS score of this vulnerability is 9.8, indicating its critical severity.

To fix this vulnerability, it is recommended to upgrade to Apache Karaf version 4.1.7 or 4.2.2.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 4.1.7 4.1.7
  • >= 4.2.0, < 4.2.2 4.2.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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