Apache Olingo Multiple Security Vulnerabilities



Date Discovered

December 4, 2019


Apache Olingo is prone to the following security vulnerabilities: 1. An XML External Entity injection vulnerability 2. A denial-of-service vulnerability 3. A remote-code execution vulnerability Attackers can exploit these issues to gain access to sensitive information, cause denial-of-service condition and execute arbitrary code in the context of the affected application. Apache Olingo versions 4.0.0 through 4.6.0 are vulnerable.

Technologies Affected

  • Apache Olingo 4.0.0
  • Apache Olingo 4.1.0
  • Apache Olingo 4.2.0
  • Apache Olingo 4.3.0
  • Apache Olingo 4.4.0
  • Apache Olingo 4.5.0
  • Apache Olingo 4.6.0


Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity including unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.

Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, do not open files that originate from untrusted sources.

Implement multiple redundant layers of security.
Use of multiple redundant layers of encryption may reduce exposure to this and other latent vulnerabilities.

Updates are available. Please see the references or vendor advisory for more information.



Archibald Haddock of Compass Security Schweiz AG and Artem Smotrakov of SAP SE

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.