VRT 391,192 CVEs tracked · 15,442 in RASP scope · data as of 19 hours ago
Reset
More filters (1)
Columns
Oracle product: Oracle Communications / Mediation Engine (glibc)
Overview 4 matches · 0 in RASP scope · 0 protected · 0 KEV · 1 public PoC · 2 CISA SSVC · 0 EPSS ≥ 0.5 · 0 disputed
4matches 0in RASP scope0.0% 0protected0.0% 0KEV0.0% 1public PoC25.0% 2CISA SSVC50.0% 0EPSS ≥ 0.50.0% 0disputed0.0%
Critical 2 50.0% High 2 50.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 1 25.0% Out of RASP scope 3 75.0% Rejected 0 0.0%
blocked by ARMR today 0 0.0% not blocked 4 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 2 50.0% Forecast only 0 0.0% No public exploit 2 50.0%
split by peak 1 / quarter
Unknown: 0None: 0Low: 0Medium: 0High: 2Critical: 2 Rejected: 0Out of RASP scope: 3Not applicable: 1Queued 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: 4blocked by ARMR today: 0 No public exploit: 2Forecast only: 0Proof of concept only: 2Working exploit published: 0Exploited in the wild: 0 Q1 2022: 1 CVE Q2 2022: 0 CVEs Q3 2022: 1 CVE Q4 2022: 0 CVEs Q1 2023: 0 CVEs Q2 2023: 0 CVEs Q3 2023: 0 CVEs Q4 2023: 0 CVEs Q1 2024: 0 CVEs Q2 2024: 1 CVE Q3 2024: 0 CVEs Q4 2024: 0 CVEs Q1 2025: 0 CVEs Q2 2025: 0 CVEs Q3 2025: 0 CVEs Q4 2025: 0 CVEs Q1 2026: 1 CVE
Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25Q3 25Q1 26
4 matches CSV JSON
CVE Severity Published Status Exploitation Description
CVE-2026-0861 High 2026-01-14 Not applicable No public exploit Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
CVE-2024-33602 High 2024-05-06 Out of RASP scope No public exploit nscd: netgroup cache assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2022-37434 Critical 2022-08-05 Out of RASP scope Proof of concept only zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).
CVE-2022-23219 Critical 2022-01-14 Out of RASP scope Proof of concept only The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its hostname argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.