CVE-2016-0779 Deserialization in n/a
Remote attackers can execute arbitrary code via crafted serialized objects in Apache TomEE, requiring an upgrade to secure the application server.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2016-0779?
CVE-2016-0779 is a critical unsafe deserialization vulnerability in n/a, published on 11 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The EjbObjectInputStream class in Apache TomEE before 1.7.4 and 7.x before 7.0.0-M3 allows remote attackers to execute arbitrary code via a crafted serialized object.
Weakness: CWE-502
Which versions are affected by CVE-2016-0779?
It affects 1 product.
Products include Apache Tomee.
How do I fix CVE-2016-0779?
No fix has been published for CVE-2016-0779 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2016-0779 being exploited?
There is no known exploitation of CVE-2016-0779 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2020-13931 Remote code execution in Apache TomEE
- CVE-2020-11969 Missing Authentication for Critical Function in Apache TomEE
- CVE-2019-13990 XML external entity injection in Terracotta Quartz Scheduler
- CVE-2019-17359 Out-of-Memory Error in Bouncy Castle Crypto
- CVE-2018-8031 Apache TomEE console vulnerable to Cross-site Scripting
Sources
Also known as CVE-2015-8581, GHSA-g7jw-7782-jjv9.