Approved changes feed: RSS · Atom
cpe:2.3:a:the_netty_project:netty:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | The Netty Project (0cf60c15-9492-5d68-a58a-34b27bb1dfbd) |
|---|---|
| Product | Netty (4940ed22-e28f-5f74-bbc6-ab247c3ed6e0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-37137 |
vulnerable | 2026-06-08 05:32:53.418809 |
Details available
The Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage. Beside this it also may buffer reserved skippable chunks until the whole chunk was received which may lead to excessive memory usage as well. This vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file) or by sending a huge skippable chunk.
Published: 2021-10-19T00:00:00.000Z
Updated: 2026-10-08T21:13:59.230Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-37136 |
vulnerable | 2026-06-08 05:32:53.398450 |
Details available
The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression). All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack
Published: 2021-10-19T00:00:00.000Z
Updated: 2026-10-08T21:13:57.388Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.