GHSA-6G43-577R-WF4X

Vulnerability from github – Published: 2026-03-18 17:26 – Updated: 2026-03-20 21:20
VLAI?
Summary
Out-of-Bounds Slice Access in free5GC CHF Leading to DoS
Details

Impact

This is an out-of-bounds slice access vulnerability in the CHF nchf-convergedcharging service. A valid authenticated request to PUT /nchf-convergedcharging/v3/recharging/:ueId?ratingGroup=... can trigger a server-side panic in github.com/free5gc/chf/internal/sbi.(*Server).RechargePut(...) due to an out-of-range slice access. In the reported runtime, Gin recovery converts the panic into HTTP 500, but the recharge path remains remotely panic-triggerable and can be abused repeatedly to degrade recharge functionality and flood logs. In deployments without equivalent recovery handling, this panic may cause more severe service disruption.

Patches

https://github.com/free5gc/chf/pull/61

Workarounds

  • Restrict access to the nchf-convergedcharging recharge endpoint to strictly trusted NF callers only.
  • Apply rate limiting or network ACLs in front of the CHF SBI interface to reduce repeated panic-trigger attempts.
  • If the recharge API is not required, temporarily disable or block external reachability to this route.
  • Ensure panic recovery, monitoring, and alerting are enabled.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/free5gc/chf"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.2.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-32937"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-129"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-18T17:26:27Z",
    "nvd_published_at": "2026-03-20T03:16:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nThis is an out-of-bounds slice access vulnerability in the CHF `nchf-convergedcharging` service.\nA valid authenticated request to PUT `/nchf-convergedcharging/v3/recharging/:ueId?ratingGroup=...` can trigger a server-side panic in `github.com/free5gc/chf/internal/sbi.(*Server).RechargePut(...)` due to an out-of-range slice access. In the reported runtime, Gin recovery converts the panic into HTTP 500, but the recharge path remains remotely panic-triggerable and can be abused repeatedly to degrade recharge functionality and flood logs. In deployments without equivalent recovery handling, this panic may cause more severe service disruption.\n\n### Patches\nhttps://github.com/free5gc/chf/pull/61\n\n### Workarounds\n- Restrict access to the `nchf-convergedcharging` recharge endpoint to strictly trusted NF callers only.\n- Apply rate limiting or network ACLs in front of the CHF SBI interface to reduce repeated panic-trigger attempts.\n- If the recharge API is not required, temporarily disable or block external reachability to this route.\n- Ensure panic recovery, monitoring, and alerting are enabled.",
  "id": "GHSA-6g43-577r-wf4x",
  "modified": "2026-03-20T21:20:37Z",
  "published": "2026-03-18T17:26:27Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/free5gc/security/advisories/GHSA-6g43-577r-wf4x"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32937"
    },
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/free5gc/issues/864"
    },
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/chf/pull/61"
    },
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/chf/commit/55af766f321a00afa978e806548c96f8a7d2433e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/free5gc/chf"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Out-of-Bounds Slice Access in free5GC CHF Leading to DoS"
}


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…