CVE-2019-17554: Improper Restriction of XML External Entity Reference in Apache Olingo

Summary

04/02/2020
Yes i
Moderate
5.5

CVE-2019-17554: Improper Restriction of XML External Entity Reference in Apache Olingo. Affects org.apache.olingo:odata-client-core versions >= 4.0.0, < 4.7.0. Fixed in 4.7.0. 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 Olingo is an open-source Java library that implements the Open Data Protocol (OData) standard. It provides a framework for building OData services and clients. The library includes modules for both server-side and client-side functionality. This vulnerability affects versions 4.0.0 to 4.6.0 of the odata-client-core and odata-server-core packages.

Vulnerability Detail

The XML content type entity deserializer in Apache Olingo versions 4.0.0 to 4.6.0 does not properly restrict the resolution of external entities. An attacker can send a request with the content type "application/xml" to trigger the deserialization of entities, which can be exploited for XML External Entity (XXE) attacks. This vulnerability has a CVSS score of 5.5 (Medium severity).

How To Fix

Minimum fixed version

4.7.0

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 recommended to apply the fix by upgrading to a non-vulnerable version of the Apache Olingo library.

Conclusion

The Apache Olingo library versions 4.0.0 to 4.6.0 are vulnerable to an XML External Entity (XXE) attack. To mitigate this vulnerability, it is recommended to upgrade to version 4.7.0 or later of the affected packages. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.olingo:odata-client-core →

Share this vulnerability

FAQ

Apache Olingo is an open-source Java library that implements the Open Data Protocol (OData) standard. It provides a framework for building OData services and clients.

XML External Entity (XXE) attack is a type of attack where an attacker can exploit vulnerabilities in XML parsers to read arbitrary files or execute remote requests.

This vulnerability allows an attacker to perform XXE attacks, which can lead to information disclosure, denial of service, or remote code execution depending on the specific scenario.

Yes, upgrading to version 4.7.0 or later of the affected packages fixes this vulnerability.

No, there are no known workarounds for this vulnerability. It is recommended to apply the fix by upgrading to a non-vulnerable version of the Apache Olingo library.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.olingo:odata-client-core.

How To Fix

Minimum fixed version

4.7.0

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