Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Potential memory exhaustion attack due to sparse slice deserialization

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/gorilla/schema 1.4.1osv · severity unknownFixed by github.com/gorilla/schema 1.4.1KEV status unknown

cve-program · CVE-2024-37298

Published

gorilla/schema converts structs to and from form values. Prior to version 1.4.1 Running `schema.Decoder.Decode()` on a struct that has a field of type `[]struct{...}` opens it up to malicious attacks regarding memory allocations, taking advantage of the sparse slice functionality. Any use of `schema.Decoder.Decode()` on a struct with arrays of other structs could be vulnerable to this memory exhaustion vulnerability. Version 1.4.1 contains a patch for the issue.

Read the publisher's advisory

euvd · EUVD-2024-2233

Published

gorilla/schema converts structs to and from form values. Prior to version 1.4.1 Running `schema.Decoder.Decode()` on a struct that has a field of type `[]struct{...}` opens it up to malicious attacks regarding memory allocations, taking advantage of the sparse slice functionality. Any use of `schema.Decoder.Decode()` on a struct with arrays of other structs could be vulnerable to this memory exhaustion vulnerability. Version 1.4.1 contains a patch for the issue.

Read the publisher's advisory

nvd · CVE-2024-37298

Published

gorilla/schema converts structs to and from form values. Prior to version 1.4.1 Running `schema.Decoder.Decode()` on a struct that has a field of type `[]struct{...}` opens it up to malicious attacks regarding memory allocations, taking advantage of the sparse slice functionality. Any use of `schema.Decoder.Decode()` on a struct with arrays of other structs could be vulnerable to this memory exhaustion vulnerability. Version 1.4.1 contains a patch for the issue.

Read the publisher's advisory

osv · GHSA-3669-72x9-r9p3

Published

### Details Running `schema.Decoder.Decode()` on a struct that has a field of type `[]struct{...}` opens it up to malicious attacks regarding memory allocations, taking advantage of the sparse slice functionality. For instance, in the Proof of Concept written below, someone can specify to set a field of the billionth element and it will allocate all other elements before it in the slice. In the local environment environment for my project, I was able to call an endpoint like `/innocent_endpoint?arr.10000000.X=1` and freeze my system from the memory allocation while parsing `r.Form`. I think [this line](https://github.com/gorilla/schema/blob/main/decoder.go#L223) is responsible for allocating the slice, although I haven't tested to make sure, so it's just an educated guess. ### Proof of Concept The following proof of concept works on both v1.2.0 and v1.2.1. I have not tested earlier versions. ```go package main import ( "fmt" "github.com/gorilla/schema" ) func main() { dec := schema.NewDecoder() var result struct { Arr []struct{ Val int } } if err := dec.Decode(&result, map[string][]string{"arr.1000000000.Val": {"1"}}); err != nil { panic(err) } fmt.Printf("%#+v\n", result) } ``` ### Impact Any use of `schema.Decoder.Decode()` on a struct with arrays of other structs could be vulnerable to this memory exhaustion vulnerability. There seems to be no possible solution that a developer using this library can do to disable this behaviour without fixing it in this project, so all uses of Decode that fall under this umbrella are affected. A fix that doesn't require a major change may also be harder to find, since it could break compatibility with some other intended use-cases.

Read the publisher's advisory

osv · GO-2024-2958

Published

Potential memory exhaustion attack due to sparse slice deserialization in github.com/gorilla/schema

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-37298

Published

schema

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "gorilla",
                    "product": "schema",
                    "versions": [
                        {
                            "version": "< 1.4.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-2233

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 1, 2024, 6:27:33 PM

dateUpdated: Aug 2, 2024, 3:50:55 AM

15 related source bulletins · separate from aliases

RHSA-2024:4963: Red Hat Security Advisory: OpenShift Container Platform 4.14.34 security update

CVE-2024-6104 · CVE-2024-37298

RHSA-2024:4848: Red Hat Security Advisory: OpenShift Container Platform 4.13.46 security update

CVE-2024-37298

RHSA-2024:6054: Red Hat Security Advisory: ACS 4.4 enhancement and security update

CVE-2024-3727 · CVE-2024-6104 · CVE-2024-37298

RHSA-2024:5258: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2023-45290 · CVE-2024-1394 · CVE-2024-3727 · CVE-2024-6104 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24789 · CVE-2024-37298 · CVE-2024-37891

RHSA-2024:4825: Red Hat Security Advisory: podman security update

CVE-2024-37298

RHSA-2024:6194: Red Hat Security Advisory: podman security update

CVE-2024-6104 · CVE-2024-24783 · CVE-2024-37298

RHSA-2024:5634: Red Hat Security Advisory: podman security update

CVE-2024-1394 · CVE-2024-6104 · CVE-2024-37298

openSUSE-SU-2025:14663-1: velociraptor-0.7.0.4.git142.862ef23-1.1 on GA media

CVE-2023-1732 · CVE-2023-44270 · CVE-2023-45133 · CVE-2023-45683 · CVE-2023-46234 · CVE-2024-21538 · CVE-2024-23331 · CVE-2024-24786 · CVE-2024-28180 · CVE-2024-31207 · CVE-2024-37298 · CVE-2024-4067 · CVE-2024-4068 · CVE-2024-42459 · CVE-2024-42460 · CVE-2024-42461 · CVE-2024-45296 · CVE-2024-45338 · CVE-2024-45811 · CVE-2024-45812 · CVE-2024-47068 · CVE-2024-47875 · CVE-2024-48948 · CVE-2024-48949 · CVE-2024-51744 · CVE-2024-55565 · CVE-2024-6104

NCSC-2024-0339: Kwetsbaarheden verholpen in Microsoft Mariner

CVE-2022-2601 · CVE-2022-3775 · CVE-2022-36648 · CVE-2019-3833 · CVE-2021-3929 · CVE-2021-4158 · CVE-2021-4206 · CVE-2021-4207 · CVE-2022-26353 · CVE-2022-35414 · CVE-2023-3354 · CVE-2022-3872 · CVE-2022-4144 · CVE-2023-45288 · CVE-2023-29404 · CVE-2023-29402 · CVE-2019-3816 · CVE-2021-3750 · CVE-2022-0358 · CVE-2022-26354 · CVE-2022-3165 · CVE-2022-2962 · CVE-2022-41722 · CVE-2022-29526 · CVE-2007-4559 · CVE-2019-9674 · CVE-2017-18207 · CVE-2019-20907 · CVE-2021-23336 · CVE-2017-17522 · CVE-2024-6655 · CVE-2024-2466 · CVE-2024-39331 · CVE-2021-43565 · CVE-2024-39277 · CVE-2024-38780 · CVE-2024-39292 · CVE-2024-39482 · CVE-2024-39484 · CVE-2024-39495 · CVE-2024-40902 · CVE-2024-41110 · CVE-2024-37298 · CVE-2024-0397 · CVE-2024-38571 · CVE-2024-42077 · CVE-2024-39473 · CVE-2024-26900 · CVE-2024-39474 · CVE-2024-42073 · CVE-2024-42074 · CVE-2024-42075 · CVE-2024-42078 · CVE-2024-0853 · CVE-2024-2004 · CVE-2024-2398 · CVE-2024-38662 · CVE-2024-36288 · CVE-2024-39480 · CVE-2024-39476 · CVE-2024-39475 · CVE-2024-37371 · CVE-2024-26461 · CVE-2024-37370 · CVE-2024-6104 · CVE-2024-6257 · CVE-2024-23722 · CVE-2024-40898 · CVE-2024-38583 · CVE-2024-39493 · CVE-2024-42068 · CVE-2024-39489 · CVE-2024-42070 · CVE-2024-42076 · CVE-2024-42080 · CVE-2024-38428 · CVE-2024-42082 · CVE-2022-48788 · CVE-2023-52340 · CVE-2022-48841 · CVE-2024-39485 · CVE-2024-39483 · CVE-2024-42071 · CVE-2024-42072 · CVE-2024-42237 · CVE-2024-42083

msrc_CVE-2024-37298: Potential memory exhaustion attack due to sparse slice deserialization

CVE-2024-37298

RHSA-2024:4702: Red Hat Security Advisory: OpenShift Container Platform 4.15.23 packages and security update

CVE-2024-37298

RHSA-2024:4858: Red Hat Security Advisory: OpenShift Container Platform 4.16.5 packages and security update

CVE-2024-6104 · CVE-2024-37298

WID-SEC-W-2024-1709: Podman: Schwachstelle ermöglicht Denial of Service

CVE-2024-37298

RHSA-2024:5202: Red Hat Security Advisory: OpenShift Container Platform 4.12.63 packages and security update

CVE-2023-45290 · CVE-2024-24790 · CVE-2024-37298

RHSA-2024:5194: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2024-6104 · CVE-2024-37298

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2024-37298

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-770

Original publisher date fields

published: 2024-07-01T19:15:04.283

lastModified: 2026-06-17T07:38:05.733

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-3669-72x9-r9p3

Published

github.com/gorilla/schema

Go

SEMVER · introduced 0 → fixed 1.4.1

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-2958

Published

github.com/gorilla/schema

Go

SEMVER · introduced 0 → fixed 1.4.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 15:59 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current