Cpe:2.3:a:http4s:http4s_ember_server:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3ahttp4shttp4s_ember_server/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 16 Sep 2026 01:05:52 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDenial of Service via Heap Exhaustion in http4s DigestAuthhttps://feed.craftedsignal.io/briefs/2026-09-http4s-digestauth-dos/Wed, 16 Sep 2026 01:05:52 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-http4s-digestauth-dos/An improper eviction logic in the http4s DigestAuth middleware allows unauthenticated remote attackers to cause heap exhaustion and service failure by triggering unbounded growth of the internal nonce map.The http4s DigestAuth server middleware contains a vulnerability in its stale-nonce cleanup mechanism, documented as CVE-2026-69208. The logic responsible for removing stale nonces uses an inverted comparison, resulting in the removal of fresh nonces while retaining stale ones indefinitely. Since the middleware generates a new nonce for every unauthenticated challenge, an attacker can intentionally flood a vulnerable service with requests to populate the nonce map. Because the stale nonces are never properly evicted, the map grows without bound until the Java Virtual Machine (JVM) experiences heap exhaustion and terminates due to an OutOfMemoryError. This vulnerability affects multiple versions of http4s-ember-server, including the 0.23.x series up to and including 0.23.34 and the 1.0.0 milestone series from 1.0.0-M1 through 1.0.0-M46. Organizations using DigestAuth should prioritize upgrading to the patched versions where the eviction logic has been corrected and a hard cache limit has been implemented.

Impact

Successful exploitation results in a persistent denial-of-service condition for the affected JVM process. This vulnerability impacts any service utilizing DigestAuth on its routes, potentially leading to widespread service unavailability if the application is targeted by high-volume, unauthenticated request bursts. Given the nature of the heap exhaustion, the leak is persistent and cannot be self-corrected by the application, requiring manual intervention or restarts to restore service until a patch is applied.

Recommendation

  • Upgrade http4s-ember-server to the latest version where the cache eviction logic is corrected and the 1,000,000 entry limit is imposed.
  • Implement a rate limiter in front of all routes protected by DigestAuth to mitigate the speed at which the nonce map can be filled while transitioning to patched versions.
  • Configure monitoring for JVM heap utilization to identify early indicators of memory growth associated with nonce map exhaustion.
  • Review application configurations to ensure that DigestAuth is only applied to routes that require authentication.
]]>lowadvisory