VRT 391,192 CVEs tracked · 15,442 in RASP scope · data as of 19 hours ago
Reset
More filters (1)
Columns
Oracle product: Oracle Fusion Middleware / Centralized Third Party Jars (Apache Maven)✕
Overview 1 match, all public PoC · 0 in RASP scope · 0 protected · 0 KEV · 0 CISA SSVC · 0 EPSS ≥ 0.5 · 0 disputed
1match, all public PoC 0in RASP scope0.0% 0protected0.0% 0KEV0.0% 0CISA SSVC0.0% 0EPSS ≥ 0.50.0% 0disputed0.0%
Critical 1 100.0% High 0 0.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 0 0.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 1 100.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 peak 1 / month
Unknown: 0None: 0Low: 0Medium: 0High: 0Critical: 1 Rejected: 0Out of RASP scope: 1Not applicable: 0Queued for review: 0Mitigated by environment configuration: 0No fix identified: 0No exploit published: 0Mitigation candidate: 0Rule in development: 0Protected by RASP: 0 unrecorded: 0not established: 0not blocked: 1blocked by ARMR today: 0 No public exploit: 1Forecast only: 0Proof of concept only: 0Working exploit published: 0Exploited in the wild: 0 April 2021: 1 CVE
Apr 21
1 match CSV JSON
CVE Severity Published▾ Status Exploitation Description
CVE-2021-26291 Critical 2021-04-23 Out of RASP scope No public exploit Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html