GHSA-7MPV-9XG6-5R79

Vulnerability from github – Published: 2025-04-07 19:09 – Updated: 2025-04-08 17:49
VLAI?
Summary
Apollo Compiler Named Fragment Processing Vulnerability
Details

Impact

Summary

A vulnerability in Apollo Compiler allowed queries with deeply nested and reused named fragments to be prohibitively expensive to validate. This could lead to excessive resource consumption and denial of service in applications.

Details

Named fragments were being processed once per fragment spread in some cases during query validation, leading to exponential resource usage when deeply nested and reused fragments were involved.

Fix/Mitigation

The validation logic has been updated to process each named fragment only once, preventing redundant traversal.

Patches

This has been remediated in apollo-compiler version 1.27.0.

Workarounds

No known direct workarounds exist.

Acknowledgements

We appreciate the efforts of the security community in identifying and improving the performance and security of query validation mechanisms.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "crates.io",
        "name": "apollo-compiler"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.27.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-31496"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-770"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-04-07T19:09:14Z",
    "nvd_published_at": "2025-04-07T21:15:42Z",
    "severity": "HIGH"
  },
  "details": "# Impact\n\n## Summary\n\nA vulnerability in Apollo Compiler allowed queries with deeply nested and reused named fragments to be prohibitively expensive to validate. This could lead to excessive resource consumption and denial of service in applications.\n\n## Details\n\nNamed fragments were being processed once per fragment spread in some cases during query validation, leading to exponential resource usage when deeply nested and reused fragments were involved.\n\n## Fix/Mitigation\n\nThe validation logic has been updated to process each named fragment only once, preventing redundant traversal.\n\n# Patches\nThis has been remediated in `apollo-compiler` version 1.27.0.\n\n# Workarounds\nNo known direct workarounds exist.\n\n## Acknowledgements\nWe appreciate the efforts of the security community in identifying and improving the performance and security of query validation mechanisms.",
  "id": "GHSA-7mpv-9xg6-5r79",
  "modified": "2025-04-08T17:49:31Z",
  "published": "2025-04-07T19:09:14Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/apollographql/apollo-rs/security/advisories/GHSA-7mpv-9xg6-5r79"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31496"
    },
    {
      "type": "WEB",
      "url": "https://github.com/apollographql/apollo-rs/pull/952"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/apollographql/apollo-rs"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Apollo Compiler Named Fragment Processing Vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…