CyberSecBulletin
CVE-2022-0084NVD status: Modified

xnio: Allocation of Resources Without Limits or Throttling

Published Updated By the CyberSecBulletin desk

CVE-2022-0084 is a high-severity allocation of resources without limits or throttling vulnerability in xnio, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected xnio versions: Fixed in v3.x. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.68% chance of exploitation within 30 days, higher than 77% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of xnio you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on access.redhat.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
XnioxnioFixed in v3.xNot stated
Red HatIntegration Camel KNot specified in the recordNot stated
Red HatIntegration Camel QuarkusNot specified in the recordNot stated
Red HatSingle Sign-on7.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Official description

A flaw was found in XNIO, specifically in the notifyReadClosed method. The issue revealed this method was logging a message to another expected end. This flaw allows an attacker to send flawed requests to a server, possibly causing log contention-related performance concerns or an unwanted disk fill-up.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How developers prevent this class of flaw

  • Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
  • Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Recent Allocation of Resources Without Limits or Throttling vulnerabilities

Spotted an error? Tell us.