Skip to content

Pomerium vulnerable to Incorrect Authorization with specially crafted requests

Critical severity GitHub Reviewed Published May 26, 2023 in pomerium/pomerium • Updated Nov 4, 2023

Package

gomod github.com/pomerium/pomerium (Go)

Affected versions

>= 0.22.0, < 0.22.2
>= 0.21.0, < 0.21.4
>= 0.20.0, < 0.20.1
>= 0.19.0, < 0.19.2
>= 0.18.0, < 0.18.1
< 0.17.4

Patched versions

0.22.2
0.21.4
0.20.1
0.19.2
0.18.1
0.17.4

Description

Impact

With specially crafted requests, incorrect authorization decisions may be made by Pomerium.

Patches

We are releasing patch fixes to address this vulnerability going back to v0.17.X. Please upgrade to:

  • v0.22.2
  • v0.21.4
  • v0.20.1
  • v0.19.2
  • v0.18.1
  • v0.17.4

For more information

If you have any questions or comments about this advisory:

References

@desimone desimone published to pomerium/pomerium May 26, 2023
Published to the GitHub Advisory Database May 26, 2023
Reviewed May 26, 2023
Published by the National Vulnerability Database May 30, 2023
Last updated Nov 4, 2023

Severity

Critical

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
Changed
Confidentiality
High
Integrity
High
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:N/S:C/C:H/I:H/A:N

EPSS score

0.840%
(82nd percentile)

Weaknesses

CVE ID

CVE-2023-33189

GHSA ID

GHSA-pvrc-wvj2-f59p

Source code

Credits

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