httparty before 0.21.0 is vulnerable to an assumed-immutable web parameter vulnerability. A remote and unauthenticated attacker can provide a crafted filename parameter during multipart/form-data uploads which could result in attacker controlled filenames being written.
Security readout for executives and security teams
Plain-English summary
CVE-2024-22049 affects the Ruby httparty package before 0.21.0. An unauthenticated remote attacker may influence filenames in multipart/form-data upload handling, causing attacker-controlled filenames to be written. The documented impact is integrity-only and rated medium, not a full system compromise.
Executive priority
Treat as a targeted dependency update, not an emergency response, unless the organization exposes upload workflows that forward untrusted filenames through vulnerable httparty versions.
Technical view
httparty before 0.21.0 has an assumed-immutable web parameter issue, mapped to CWE-472. Crafted multipart/form-data filename input can tamper with generated request data and affect written filenames. The source bundle identifies a vendor advisory and patch commit; version 0.21.0 is the fixed release.
Likely exposure
Exposure is most likely in Ruby applications, services, or OS packages using httparty before 0.21.0 with multipart/form-data upload flows involving untrusted filename input. Systems not using httparty multipart uploads are less likely exposed.
Exploitation context
The provided bundle does not cite active exploitation, and KEV is false. CVSS indicates network reachability, low attack complexity, no privileges, and no user interaction, but only low integrity impact with no stated confidentiality or availability impact.
Researcher notes
Evidence is limited to advisories, CVE metadata, package announcements, and a patch reference. The bundle does not provide proof-of-concept details or exploitation telemetry. Validate exposure by dependency version and multipart upload data flow.
Mitigation direction
Upgrade httparty to 0.21.0 or later.
Apply relevant Fedora or Debian package updates where httparty is OS-managed.
Review vendor advisory guidance before relying on compensating controls.
Avoid passing untrusted filenames into multipart upload flows without validation.
Validation and detection
Inventory Gemfile.lock, gemspecs, containers, and OS packages for httparty versions.
Confirm deployed runtime uses httparty 0.21.0 or later.
Identify code paths that build multipart/form-data requests with user-supplied filenames.
Check package manager advisories for applicable Fedora or Debian fixed builds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-472: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-472 · source CWE mapping
External Control of Assumed-Immutable Web Parameter
External Control of Assumed-Immutable Web Parameter represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.