Skip to content

Denial of Service vulnerability in @podium/layout and @podium/proxy

High severity GitHub Reviewed Published Apr 6, 2022 in podium-lib/proxy • Updated Jan 27, 2023

Package

npm @podium/layout (npm)

Affected versions

< 4.6.110

Patched versions

4.6.110
npm @podium/proxy (npm)
< 4.2.74
4.2.74

Description

Impact

An attacker using the Trailer header as part of the request against proxy endpoints has the ability to take down the server.
All Podium layouts that include podlets with proxy endpoints are affected.

Patches

@podium/layout which is the main way developers/users are vulnerable to this exploit, has been patched in version 4.6.110. All earlier versions are vulnerable.
@podium/proxy which is the source of the vulnerability and is used by @podium/layout has been patched in version 4.2.74. All earlier versions are vulnerable.

Workarounds

It is not easily possible to work around this issue without upgrading. We recommend upgrading @podium/layout and/or @podium/proxy as soon as possible.

For more information

If you have any questions or comments about this advisory:

Credits

The vulnerability was reported by krynos from Ercoli Consulting via FINN.no's private bug bounty program

References

@emilva emilva published to podium-lib/proxy Apr 6, 2022
Published by the National Vulnerability Database Apr 6, 2022
Published to the GitHub Advisory Database Apr 7, 2022
Reviewed Apr 7, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.235%
(62nd percentile)

Weaknesses

CVE ID

CVE-2022-24822

GHSA ID

GHSA-3hjg-vc7r-rcrw

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.