Skip to content

Excessive CPU usage

High severity GitHub Reviewed Published Sep 9, 2021 in pomerium/pomerium • Updated Feb 1, 2023

Package

gomod github.com/pomerium/pomerium (Go)

Affected versions

< 0.14.8
= 0.15.0

Patched versions

0.14.8
0.15.1

Description

Envoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity. This can lead to high CPU utilization when a large number of streams are reset.

Impact

This can result in a DoS condition.

Patches

Pomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched.

Workarounds

N/A

References

envoy GSA
envoy CVE
envoy announcement

For more information

If you have any questions or comments about this advisory:

References

@travisgroth travisgroth published to pomerium/pomerium Sep 9, 2021
Published by the National Vulnerability Database Sep 9, 2021
Reviewed Sep 10, 2021
Published to the GitHub Advisory Database Sep 10, 2021
Last updated Feb 1, 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.142%
(51st percentile)

Weaknesses

CVE ID

CVE-2021-39204

GHSA ID

GHSA-5wjf-62hw-q78r

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.