The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade org.apache.camel:camel-neo4j to version 4.14.8, 4.18.3, 4.21.0 or higher.
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Data Query Logic in the Neo4jProducer.retrieveNodes and deleteNode processes when JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation. An attacker can execute arbitrary Cypher queries and read, modify, or delete any node or relationship in the Neo4j database by supplying specially crafted JSON key names. This is only exploitable if a route maps untrusted input into the CamelNeo4jMatchProperties map, such as by passing a request body as the match map or from a consumer that does not filter inbound Camel* headers, allowing an external sender to influence the header.
This vulnerability can be mitigated by validating or allow-listing property names (for example, against the pattern ^[A-Za-z_][A-Za-z0-9_]$) before the Neo4j producer, and ensuring that any consumer feeding such a route filters inbound Camel / camel* headers so the match header cannot be supplied by an external sender.