attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is none; integrity impact is none; availability impact is high.
Affected products
suse Rancher
Classified as
CWE-770 (Allocation of Resources Without Limits or Throttling)
Affected Products, Subsystems & Sectors
Vendor
Product
Affected Versions
Patch Status
suse
Rancher
Subsystems
General OT
Sectors
Multiple
What to Know
When API audit logging is enabled, the middleware reads the entire HTTP request body into memory without enforcing a size limit on login endpoints. Because the audit middleware is positioned earlier in the handler chain than Rancher's APIBodyLimitingHandler, the body-size cap (default 1 MiB) is bypassed for requests that pass through the audit copyReqBody path. An unauthenticated attacker can send arbitrarily large request bodies to the public login endpoints, causing the Rancher Manager server process to allocate memory proportional to the supplied body size. With just a few concurrent connections, this can exhaust available memory and terminate the Rancher Manager plane process, making the Rancher API and UI unavailable and interrupting management of all downstream clusters. (NVD)
What to Do
Monitor suse's web page for any future patch releases.