Oracle Communications Applications / Transformation for PDC (Apache Tomcat) CVEs

VRT 391,192 CVEs tracked · 15,442 in RASP scope · data as of 19 hours ago

Description contains RASP scope Status Exploitation Severity

Reset

Overview 1 match, all in RASP scope, all public PoC · 0 protected · 0 KEV · 0 CISA SSVC · 0 EPSS ≥ 0.5 · 0 disputed

1match, all in RASP scope, all public PoC 0protected0.0% 0KEV0.0% 0CISA SSVC0.0% 0EPSS ≥ 0.50.0% 0disputed0.0%

Critical 0 0.0% High 1 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%

Protected by RASP 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 100.0% No fix identified 0 0.0% Mitigated by environment configuration 0 0.0% Queued for review 0 0.0% Not applicable 0 0.0% Out of RASP scope 0 0.0% Rejected 0 0.0%

blocked by ARMR today 0 0.0% not blocked 1 100.0% not established 0 0.0% unrecorded 0 0.0%

Exploited in the wild 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 100.0%

split by SeverityStatusProtectionExploit maturity peak 1 / month

Dec 20

1 match CSV JSON

CVE	Severity	Published▾	Status	Exploitation	Description
CVE-2020-17527	High	2020-12-03	No exploit published	No public exploit	While investigating bug 64830 it was discovered that Apache Tomcat 10.0.0-M1 to 10.0.0-M9, 9.0.0-M1 to 9.0.39 and 8.5.0 to 8.5.59 could re-use an HTTP request header value from the previous stream received on an HTTP/2 connection for the request associated with the subsequent stream. While this would most likely lead to an error and the closure of the HTTP/2 connection, it is possible that information could leak between requests.

CVE

Severity

Published▾

Status

Exploitation

Description

CVE-2020-17527

High

2020-12-03

No exploit published

No public exploit

While investigating bug 64830 it was discovered that Apache Tomcat 10.0.0-M1 to 10.0.0-M9, 9.0.0-M1 to 9.0.39 and 8.5.0 to 8.5.59 could re-use an HTTP request header value from the previous stream received on an HTTP/2 connection for the request associated with the subsequent stream. While this would most likely lead to an error and the closure of the HTTP/2 connection, it is possible that information could leak between requests.