Skip to content

pomerium_signature is not verified in middleware in github.com/pomerium/pomerium

Moderate severity GitHub Reviewed Published Mar 31, 2021 in pomerium/pomerium • Updated Oct 2, 2023

Package

gomod github.com/pomerium/pomerium (Go)

Affected versions

>= 0.10.0, < 0.13.4

Patched versions

0.13.4

Description

Impact

Some API endpoints under /.pomerium/ do not verify parameters with pomerium_signature. This could allow modifying parameters intended to be trusted to Pomerium.

The issue mainly affects routes responsible for sign in/out, but does not introduce an authentication bypass.

Specific Go Packages Affected

github.com/pomerium/pomerium/authenticate

Patches

Patched in v0.13.4

For more information

If you have any questions or comments about this advisory

References

@travisgroth travisgroth published to pomerium/pomerium Mar 31, 2021
Reviewed May 20, 2021
Published to the GitHub Advisory Database May 21, 2021
Last updated Oct 2, 2023

Severity

Moderate

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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:R/S:C/C:L/I:L/A:N

EPSS score

0.078%
(35th percentile)

Weaknesses

CVE ID

CVE-2021-29652

GHSA ID

GHSA-fv82-r8qv-ch4v

Source code

No known source code

Credits

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