Sharpippnext
Approved changes feed: RSS · Atom
cpe:2.3:a:danielklecha:sharpippnext:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Danielklecha (5abe5e10-8cc0-5e3d-b7ea-51f4f379a392) |
|---|---|
| Product | Sharpippnext (098043ad-087b-5ec4-a76c-22fc7f25c394) |
| 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-2026-59975 |
vulnerable | 2026-11-19 05:27:34.375617 |
SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service
HIGH (7.5)
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.
Published: 2026-11-18T20:25:07.895Z
Updated: 2026-11-18T20:54:17.088Z 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.