Denial of service via oversized token name
Published Sep 30, 2022 · Updated May 20, 2025
Allocation of resources without limits in Rdiffweb before 2.5.0a3 allows remote attackers to cause denial of service via an oversized token name. The token-creation form accepted an arbitrarily long Token name value; the upstream fix adds a 256-character validator, preventing unbounded allocation during request processing. No authentication is required according to the published network vector, so a reachable instance can be forced into resource exhaustion or memory corruption, interrupting service.
Summary
What happened
Allocation of resources without limits in Rdiffweb before 2.5.0a3 allows remote attackers to cause denial of service via an oversized token name. The token-creation form accepted an arbitrarily long Token name value; the upstream fix adds a 256-character validator, preventing unbounded allocation during request processing. No authentication is required according to the published network vector, so a reachable instance can be forced into resource exhaustion or memory corruption, interrupting service.
The record
- CVE
- CVE-2022-3371
- Published
- Sep 30, 2022
- Updated
- May 20, 2025
- Vendor
- IKUS Software
- Product
- Rdiffweb
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2022CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.5.0a3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo