SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| danielklecha | SharpIppNext | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Danielklecha | Sharpippnext |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-3h63-w8jq-rrf2 | SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.623% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Danielklecha
Danielklecha sharpippnext |
|
| Vendors & Products |
Danielklecha
Danielklecha sharpippnext |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SharpIppNext is a .NET Standard library for building Internet Printing Protocol clients and servers. Prior to 4.1.0, server-side SharpIppNext implementations using SharpIppServer.ReceiveRequestAsync or SharpIppServer.ReceiveRawRequestAsync pass incoming data to IppProtocol.ReadIppRequestAsync in SharpIpp/Protocol/IppProtocol.cs, where ReadDocumentStream is enabled by default and the remaining document body is copied with CopyToAsync into a MemoryStream without a size limit. An unauthenticated remote client can send an arbitrarily large IPP document body, exhausting process memory and causing an out-of-memory failure or service termination. Client-only implementations using SharpIppClient are not affected. This issue is fixed in version 4.1.0. | |
| Title | SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service | |
| Weaknesses | CWE-400 | |
| References |
|
|
| Metrics |
cvssV3_1
|