WaratekVRT Sign in

Oracle Financial Services Applications Common Core (Netty) CVEs

2 CVEs, 1 exploited

Reset
More filters (1)
Columns
Oracle product: Oracle Financial Services Applications / Common Core (Netty)✕
Overview 2 matches · 0 protected · 1 exploited · 1 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
2matches 0protected0.0% 1exploited50.0% 1CISA KEV50.0% 1public PoC50.0% 1EPSS ≥ 0.550.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 1 50.0% No exploit published 1 50.0%
Critical 0 0.0% High 1 50.0% Medium 1 50.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 2 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 50.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 50.0%
split by peak 1 / month
No exploit published: 1Mitigation candidate: 1 Medium: 1High: 1 not blocked: 2 No public exploit: 1Exploited: 1
Jun 231 No exploit published1 Medium1 not blocked1 No public exploit1 Jul 230 Aug 230 Sep 230 Oct 231 Mitigation candidate1 High1 not blocked1 Exploited1
Jun 23Jul 23Aug 23Sep 23Oct 23
2 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2023-44487 High 2023-10-10 Mitigation candidate Exploited The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
CVE-2023-34462 Medium 2023-06-22 No exploit published No public exploit Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The `SniHandler` can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the `SniHandler` to allocate 16MB of heap. The `SniHandler` class is a handler that waits for the TLS handshake to configure a `SslHandler` according to the indicated server name by the `ClientHello` record. For this matter it allocates a `ByteBuf` using the value defined in the `ClientHello` record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the `SslClientHelloHandler`. This vulnerability has been fixed in version 4.1.94.Final.