httparty में संभावित SSRF भेद्यता जो API कुंजी रिसाव की ओर ले जाती है

The SSRF vulnerability in httparty allows an attacker to craft malicious requests that bypass the intended restrictions on outbound connections. By manipulating the path argument to an absolute URL, an attacker can force httparty to send requests to arbitrary internal or external hosts. This can lead to several severe consequences, including the leakage of API keys or other sensitive credentials stored within the application. Furthermore, an attacker could potentially use this vulnerability to interact with internal services that are not directly exposed to the internet, facilitating lateral movement within the network. The ability to issue requests to internal servers without proper authentication or authorization significantly expands the attack surface.

Applications utilizing the httparty Ruby gem in versions 0.9.0 and earlier are at risk. This includes web applications, APIs, and any other Ruby projects that rely on httparty for making HTTP requests. Shared hosting environments where multiple applications share the same Ruby environment are particularly vulnerable, as a compromise of one application could potentially expose the entire environment.

• ruby / server:

  grep -r 'require \'httparty\' ' /path/to/your/ruby/projects

• ruby / supply-chain:

  gem list httparty

• generic web:

  curl -I <your_application_url>/<potentially_vulnerable_endpoint>
  # Check for unexpected internal hostnames in the response headers

1. 2025-12-23Disclosure

   disclosure

1. आरक्षित2025-12-23
2. प्रकाशित2025-12-23
3. संशोधित2026-04-10
4. EPSS अद्यतन2026-03-23

The primary mitigation for CVE-2025-68696 is to upgrade to httparty version 0.24.0 or later, which includes the fix for this vulnerability. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) or proxy to filter outbound requests and block those targeting internal resources. Additionally, carefully validate and sanitize any user-supplied input that is used to construct URLs. Review your application's code to ensure that the baseuri is properly enforced and that no other mechanisms exist that could bypass this restriction. After upgrading, confirm the fix by attempting to craft a request with an absolute URL and verifying that the baseuri is correctly applied.