Repository navigation
Update dependency httparty to v0.24.0 [SECURITY] - #26
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.22.0→0.24.0httparty Has Potential SSRF Vulnerability That Leads to API Key Leakage
CVE-2025-68696 / GHSA-hm5p-x4rq-38w4
More information
Details
Summary
There may be an SSRF vulnerability in httparty. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers.
Details
When httparty receives a path argument that is an absolute URL, it ignores the
base_urifield. As a result, if a malicious user can control the path value, the application may unintentionally communicate with a host that the programmer did not anticipate.Consider the following example of a web application:
Now, suppose an attacker sends a request like this:
In this case, httparty sends the
X-API-KEYnot tohttp://example.testbut instead tohttp://attacker.test.A similar problem was reported and fixed in the HTTP client library axios in the past:
https://redirect.github.com/axios/axios/issues/6463
Also, Python's
urljoinfunction has documented a warning about similar behavior:https://docs.python.org/3.13/library/urllib.parse.html#urllib.parse.urljoin
PoC
Follow these steps to reproduce the issue:
Set up two simple HTTP servers.
Create a script (for example,
main.rb):Run the script:
Although
base_uriis set tohttp://localhost:10001/, httparty sends the request tohttp://localhost:10002/.Impact
base_uriand does not properly validate the path parameter may be affected by this issue.Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:PReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
jnunemaker/httparty (httparty)
v0.24.0Compare Source
What's Changed
Full Changelog: jnunemaker/httparty@v0.23.2...v0.24.0
v0.23.2: 0.23.2Compare Source
What's Changed
New Contributors
Full Changelog: jnunemaker/httparty@v0.23.1...v0.23.2
v0.23.1Compare Source
d268387Full Changelog: jnunemaker/httparty@v0.23.0...v0.23.1
v0.23.0Compare Source
What's Changed
New Contributors
Full Changelog: jnunemaker/httparty@v0.22.0...v0.23.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.