Insecure deserializaiton in the httpx Ruby gem via unsafe Oj object-mode
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| os85 | httpx | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
Upgrade to httpx 1.9.1, which calls Oj.load with an explicit { mode: :strict } default. If upgrading is not possible, pass a safe mode at the call site (response.json(mode: :strict)), or set a safe process-wide default such as Oj.default_options = { mode: :strict } (or :rails) before any untrusted JSON is parsed. Do not rely on Oj's shipped :object default for data that arrived over the network.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The httpx Ruby gem parses JSON response bodies through its transcoder layer. HTTPX::Response#json delegates to Transcoder::JSON.decode, and when the oj gem is loaded and multi_json is absent, the decoder falls back to json_load, which calls Oj.load(response.to_s) with no mode option. Oj.load defaults to :object mode, in which a response document can allocate any already-loaded Ruby class ("^o":"ClassName") and set its instance variables, or resolve a class or module reference ("^c":"Name"). An attacker who controls, or can influence, the URL an application fetches with HTTPX.get(url).json therefore controls object instantiation in the victim process. With a matching gadget chain, this issue can potentially cause remote code execution. Affects httpx 1.9.0; fixed in 1.9.1. | |
| Title | Insecure deserializaiton in the httpx Ruby gem via unsafe Oj object-mode | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV3_1
|