AIKIDO-2026-412779
SharpIppNext is vulnerable to Uncontrolled Resource Consumption
75
High Risk
This Affects:
SharpIppNextTL;DR
The IPP protocol layer's request reader copies the entire attacker-supplied IPP document payload into an in-memory stream with no size limit. Because document buffering is enabled by default and the documented server setup passes an unauthenticated HTTP request body straight into the receive path, a remote attacker can send an arbitrarily large request body to exhaust process memory. This can trigger an out-of-memory condition that crashes the host process and makes the IPP service unavailable. The fix adds a configurable maximum document size that rejects oversized payloads with a request-entity-too-large error.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you expose a server-side IPP endpoint using SharpIppServer to parse incoming requests.
Background info
SharpIppNext is vulnerable to Uncontrolled Resource Consumption in versions 0.0.1 - 4.0.2.
How to fix this
Upgrade the SharpIppNext library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant