@hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

@hapi/content provides HTTP Content-* header parsing. From 3.0.6 until 6.0.3, Content.disposition() uses an unanchored parameter-name expression in a global regular-expression scan, causing repeated failed matching over the remaining input when a Content-Disposition parameter contains a long token without an equals sign. The resulting quadratic processing can block the Node.js event loop before route handlers or validation when @hapi/pez parses multipart/form-data headers, including unauthenticated hapi routes with payload.multipart enabled, and also affects applications that pass untrusted headers directly to Content.disposition(). This issue is fixed in @hapi/content version 6.0.3.

[ Fixes ]Fixes and patches

• @hapi/content 6.0.3Fixed version · GitHub Advisories · npm package @hapi/content: upgrade to 6.0.3 or later (affected <= 6.0.2)

[ Packages ]Affected open-source packages

• @hapi/content npmAffected <= 6.0.2 · fixed in 6.0.3 · GHSA-8494-f6mr-cjpv
• content npmAffected >= 3.0.6, <= 4.0.6 · GHSA-8494-f6mr-cjpv

[ References ]References

• github.com/hapijs/content/commit/0993851dc7234976a3fce3a7c31662b213c940fd
• github.com/hapijs/content/releases/tag/v6.0.3
• github.com/hapijs/content/security/advisories/GHSA-8494-f6mr-cjpv