CVE-2024-39315: Github.com/pomerium/pomerium Pomerium Exposed OAuth2 Access And Vulnerability

MODERATE
Advisory Identifier: GHSA-rrqr-7w59-637v
Share
CVSS 5.7
CWE-201
Published
Advisory Summary

CVE-2024-39315 is a MODERATE (CVSS 5.7) pomerium exposed oauth2 access and vulnerability (CWE-201: Insertion of Sensitive Information Into Sent Data) affecting Github.com/pomerium/pomerium libraries in the Go ecosystem. The issue involves pomerium exposed oauth2 access and id tokens in user info endpoint response. Remediation is available by upgrading affected packages to version 0.26.1.

CVE-2024-39315 at a Glance

CVE Identifier CVE-2024-39315
GHSA Identifier GHSA-rrqr-7w59-637v
Severity MODERATE
CVSS v3.1 Base Score 5.7
CWE Classification CWE-201: Insertion of Sensitive Information Into Sent Data
Affected Product Github.com/pomerium/pomerium
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-39315

To remediate this vulnerability, upgrade all affected Github.com/pomerium/pomerium dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/pomerium/pomerium fixed: 0.26.1 
Upgrade github.com/pomerium/pomerium to 0.26.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/pomerium/pomerium

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-39315, inspect your project dependencies for Github.com/pomerium/pomerium:

inspect dependencies for github.com/pomerium/pomerium

Analyze the terminal output to locate any version of Github.com/pomerium/pomerium in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.26.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-201: Insertion of Sensitive Information Into Sent Data, where the code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. In Github.com/pomerium/pomerium, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact The Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users. This issue may be more severe in the presence of an XSS vulnerability in an upstream application proxied through Pomerium. If an attacker could insert a malicious script onto a web page proxied through Pomerium, that script could access these tokens by making a request to the `/.pomerium` endpoint. Upstream applications that authenticate only the ID token may be vulnerable to user impersonation using a token obtained in this manner. Note that an OAuth2 access token or ID token by itself is not sufficient to hijack a user's Pomerium session. Upstream applications should not be vulnerable to user impersonation via these tokens provided: - the application verifies the [Pomerium JWT](https://www.pomerium.com/docs/capabilities/getting-users-identity) for each request, - the connection between Pomerium and the application is secured by mTLS, - or the connection between Pomerium and the application is otherwise secured at the network layer. ### Patches Patched in Pomerium v0.26.1. ### Workarounds None ### For more information If you have any questions or comments about this advisory: - Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues) - Email us at [security@pomerium.com](mailto:security@pomerium.com) Credit to Vadim Sheydaev, aka Enr1g for reporting this issue.

CVE-2024-39315 Affected Github.com/pomerium/pomerium Versions

1 component(s)
Fixed Versions:
0.26.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/pomerium/pomerium
golang/github.com/pomerium/pomerium
Go
< 0.26.1
0.26.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/pomerium/pomerium/security/advisories/GHSA-rrqr-7w59-637v
NVD — CVE-2024-39315 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-39315
Security Fix Commit FIX COMMIT
https://github.com/pomerium/pomerium/commit/4c7c4320afb2ced70ba19b46de1ac4383f3daa48
Github.com/pomerium/pomerium Source Repository REPOSITORY
https://github.com/pomerium/pomerium

Frequently Asked Questions

What is CVE-2024-39315?
CVE-2024-39315 is a security vulnerability in Github.com/pomerium/pomerium involving Pomerium exposed OAuth2 access and ID tokens in user info endpoint response under CWE-201: Insertion of Sensitive Information Into Sent Data.
Which Github.com/pomerium/pomerium versions are affected?
Affected versions include releases prior to 0.26.1 across affected packages: github.com/pomerium/pomerium.
What version fixes CVE-2024-39315?
Upgrading to 0.26.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/pomerium/pomerium affected?
Yes, github.com/pomerium/pomerium is affected in releases prior to 0.26.1. Upgrade your dependency to 0.26.1 or later.
What is the CVSS score of CVE-2024-39315?
CVE-2024-39315 has a CVSS v3.1 base score of 5.7 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2024-39315?
CVE-2024-39315 is classified under CWE-201: Insertion of Sensitive Information Into Sent Data (The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.).
How can I check Go dependencies for CVE-2024-39315?
Run the dependency tree command: 'inspect dependencies for github.com/pomerium/pomerium'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rrqr-7w59-637v",
  "modified" : "2025-04-11T23:46:26Z",
  "published" : "2024-07-05T19:42:11Z",
  "aliases" : [ "CVE-2024-39315" ],
  "summary" : "Pomerium exposed OAuth2 access and ID tokens in user info endpoint response",
  "details" : "### Impact\n\nThe Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users.\n\nThis issue may be more severe in the presence of an XSS vulnerability in an upstream application proxied through Pomerium. If an attacker could insert a malicious script onto a web page proxied through Pomerium, that script could access these tokens by making a request to the `/.pomerium` endpoint.\n\nUpstream applications that authenticate only the ID token may be vulnerable to user impersonation using a token obtained in this manner.\n\nNote that an OAuth2 access token or ID token by itself is not sufficient to hijack a user's Pomerium session. Upstream applications should not be vulnerable to user impersonation via these tokens provided:\n- the application verifies the [Pomerium JWT](https://www.pomerium.com/docs/capabilities/getting-users-identity) for each request,\n- the connection between Pomerium and the application is secured by mTLS,\n- or the connection between Pomerium and the application is otherwise secured at the network layer.\n\n### Patches\nPatched in Pomerium v0.26.1.\n\n### Workarounds\nNone\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)\n- Email us at [security@pomerium.com](mailto:security@pomerium.com)\n\nCredit to Vadim Sheydaev, aka Enr1g for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/pomerium/pomerium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.26.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pomerium/pomerium/security/advisories/GHSA-rrqr-7w59-637v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-39315"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pomerium/pomerium/commit/4c7c4320afb2ced70ba19b46de1ac4383f3daa48"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pomerium/pomerium"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-201" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-07-05T19:42:11Z",
    "nvd_published_at" : "2024-07-02T20:15:06Z"
  }
}