GHSA-PW25-C82R-75MM

Vulnerability from github – Published: 2025-08-25 21:48 – Updated: 2025-08-26 17:12
VLAI?
Summary
request-filtering-agent SSRF Bypass via HTTPS Requests to 127.0.0.1
Details

request-filtering-agent versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked.

Impact:

Vulnerable patterns (requests that should be blocked but are allowed): - https://127.0.0.1:443/api - https://127.0.0.1:8443/admin - Any HTTPS request using direct IP address https://127.0.0.1

This vulnerability primarily affects services using self-signed certificates on 127.0.0.1.

Not affected (correctly blocked in all versions): - http://127.0.0.1:80/api - HTTP requests are properly blocked - https://localhost:443/api - Domain-based requests trigger DNS lookup and are blocked - http://localhost:80/api - Domain-based HTTP requests are blocked - Requests to other private IPs like 192.168.x.x, 10.x.x.x, 172.16.x.x

This allows attackers to potentially access internal HTTPS services running on localhost, bypassing the library's SSRF protection. The vulnerability is particularly dangerous when the application accepts user-controlled URLs and internal services are only protected by network-level restrictions.

Fixed in 2.0.0

This vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.

Root Cause:The HTTPS agent fails to validate direct IP addresses like https://127.0.0.1 during TLS connection setup, allowing them to bypass the security filter.

Details: https://github.com/azu/request-filtering-agent-https127-test

Thanks Luca

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "request-filtering-agent"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-57814"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-08-25T21:48:01Z",
    "nvd_published_at": "2025-08-25T22:15:33Z",
    "severity": "MODERATE"
  },
  "details": "request-filtering-agent versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked.\n\n**Impact:**\n\nVulnerable patterns (requests that should be blocked but are allowed):\n- https://127.0.0.1:443/api\n- https://127.0.0.1:8443/admin\n- Any HTTPS request using direct IP address `https://127.0.0.1`\n\nThis vulnerability primarily affects services using self-signed certificates on `127.0.0.1`.\n\n**Not affected (correctly blocked in all versions):**\n- http://127.0.0.1:80/api - HTTP requests are properly blocked\n- https://localhost:443/api - Domain-based requests trigger DNS lookup and are blocked\n- http://localhost:80/api - Domain-based HTTP requests are blocked\n- Requests to other private IPs like 192.168.x.x, 10.x.x.x, 172.16.x.x\n\nThis allows attackers to potentially access internal HTTPS services running on localhost, bypassing the library\u0027s SSRF protection. The vulnerability is particularly dangerous when the application accepts user-controlled URLs and internal services are only protected by network-level restrictions.\n\n## Fixed in 2.0.0\n\nThis vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.\n\nRoot Cause:The HTTPS agent fails to validate direct IP addresses like `https://127.0.0.1` during TLS connection setup, allowing them to bypass the security filter.\n\nDetails: https://github.com/azu/request-filtering-agent-https127-test\n\nThanks Luca",
  "id": "GHSA-pw25-c82r-75mm",
  "modified": "2025-08-26T17:12:50Z",
  "published": "2025-08-25T21:48:01Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/azu/request-filtering-agent/security/advisories/GHSA-pw25-c82r-75mm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-57814"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/azu/request-filtering-agent"
    },
    {
      "type": "WEB",
      "url": "https://github.com/azu/request-filtering-agent-https127-test"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P",
      "type": "CVSS_V4"
    }
  ],
  "summary": "request-filtering-agent SSRF Bypass via HTTPS Requests to 127.0.0.1"
}


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…