Deploy autonomous AI agents that reason, exploit, and validate complex vulnerability chains — not another scanner, an agentic system that thinks like a senior pentester.
CVE-2022-23302 is a high severity vulnerability with a CVSS score of 8.8. No known exploits currently, and patches are available.
Very high probability of exploitation in the next 30 days
EPSS predicts the probability of exploitation in the next 30 days based on real-world threat data, complementing CVSS severity scores with actual risk assessment.
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
| Vendor | Product |
|---|---|
| Oracle | Financial Services Revenue Management And Billing Analytics |
Please cite this page when referencing data from Strobes VI. Proper attribution helps support our vulnerability intelligence research.
| Broadcom |
| Brocade Sannav |
| Oracle | Business Intelligence |
| Oracle | Weblogic Server |
| Oracle | E Business Suite Cloud Manager And Cloud Backup Module |
| Oracle | Enterprise Manager Base Platform |
| Oracle | Business Process Management Suite |
| Oracle | Communications Unified Inventory Management |
| Oracle | Identity Management Suite |
| Oracle | Hyperion Data Relationship Management |
And 16 more...