chore(deps): update httparty to 0.24.0 (CVE-2025-68696)#45
Open
mapup-security-fix-bot[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update httparty to 0.24.0 (CVE-2025-68696)#45mapup-security-fix-bot[bot] wants to merge 1 commit intomainfrom
mapup-security-fix-bot[bot] wants to merge 1 commit intomainfrom
Conversation
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.
Security Fix: CVE-2025-68696 —
httpartyupgraded to 0.24.0Vulnerability Summary
httparty(RubyGems)<= 0.23.20.24.00.18.1What Changed
Gemfile.lockin theruby/subdirectory to resolvehttpartyat0.24.0viabundle update httparty.Gemfileconstraint (>= 0.21.0) already permits0.24.0; noGemfileedit was required.Notes for Reviewer
0.18.1→0.24.0). This is a significant version jump; please verify application behaviour.CHANGELOGin the repo to confirm API compatibility. Recommend reviewing the httparty releases for any breaking changes between0.18.1and0.24.0.gitleaks.yml,semgrep.yml) are security-scan-only; there are no automated Ruby tests to catch regressions. Manual testing of routes usinghttpartycalls is advised before merging.References