Archive
2 June 2021
Vulnerabilities first published on this day (UTC), newest first.
9 results · Clear filters · Feed
-
High 8.8
IBM Jazz Foundation and IBM Engineering products could allow a remote attacker to bypass security restrictions, caused …
-
High 7.5
Redis vulnerability in STRALGO LCS on 32-bit systems
Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. An integer overflow bug in Redis version 6.0 or newer, could be exploited using the STRALGO LCS command to corrupt the heap and potentially …
-
High 7.5
Directory traversal in Eclipse Mojarra
Directory traversal in Eclipse Mojarra before 2.3.14 allows attackers to read arbitrary files via the loc parameter or con parameter.
-
High 7.5
Uncontrolled Resource Consumption in Pillow
An issue was discovered in Pillow before 8.2.0. For EPS data, the readline implementation used in EPSImageFile has to deal with any combination of \r and \n as line endings. It used an accidentally quadratic method of accumulating lines while looking for a li…
-
High 7.5
Uncontrolled Resource Consumption in jboss-remoting
A flaw was found in jboss-remoting in versions before 5.0.20.SP1-redhat-00001. A malicious attacker could cause threads to hold up forever in the EJB server by writing a sequence of bytes corresponding to the expected messages of a successful EJB client reque…
-
High 7.5
RESTEasy 4.5.5.Final in hash flooding
A vulnerability was found in RESTEasy, where RootNode incorrectly caches routes. This issue results in hash flooding, leading to slower requests with higher CPU time spent searching and adding the entry. This flaw allows an attacker to cause a denial of servi…
-
High 7.2
Improper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability in PHP component in …
-
High 7.7
Improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in file management compone…
-
High 7.5
Potential infinite loop in Pillow
An issue was discovered in Pillow before 8.2.0. For FLI data, FliDecode did not properly check that the block advance was non-zero, potentially leading to an infinite loop on load.