BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-24536High confidence

Excessive resource consumption in net/http, net/textproto and mime/multipart

Go standard library · mime/multipart

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.48% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Go standard library mime/multipart and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitygoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.20.3-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitygoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.20.3-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communitygoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.20.3-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian bookwormbookworm · sourcegolang-1.19Vendor fix publishedDebian records a fixed source-package version for this release.1.19.8-2Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-24536 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygolang: net/http, net/textproto, mime/multipart: denial of service from excessive resource consumption
101 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • workload-availability/node-healthcheck-rhel8-operator as a component of Node HealthCheck Operator
  • workload-availability/node-maintenance-rhel8-operator as a component of Node Maintenance Operator
  • helm.src as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
  • odo.src as a component of OpenShift Developer Tools and Services
  • openshift-pipelines-client.src as a component of OpenShift Pipelines
  • openshift-golang-builder-container as a component of OpenShift Service Mesh 2
  • 3scale-operator-container as a component of Red Hat 3scale API Management Platform 2
  • thanos-contain.src as a component of Red Hat Advanced Cluster Management for Kubernetes 2
  • advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • amq-broker-rhel8-operator-container as a component of Red Hat AMQ Broker 7
  • receptor.src as a component of Red Hat Ansible Automation Platform 2
Summary
A flaw was found in Golang Go, where it is vulnerable to a denial of service caused by an issue during multipart form parsing. By sending a specially crafted input, a remote attacker can consume large amounts of CPU and memory, resulting in a denial of service.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-28552

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

What

Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Uncontrolled Resource Consumption → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-400
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-2031Xerox FreeFlow Print Server: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1378Red Hat OpenShift Container Platform: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in der Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2023-1373Red Hat OpenStack Platform : Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in der Red Hat OpenStack Platform ausnutzen, um seine Privilegien zu erhöhen, einen Denial of Service zu verursachen oder Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20230412Security Bulletin 12 Apr 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Apr 2023, published on 12 April 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0339Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-41717 Référence CVE CVE-2022-41720 https://www.cve.org/CVERecord?id=CVE-2022-41720 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2022-41724 https://www.cve.org/CVERecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2023-24531 https://www.cve.org/CVERecord?id=CVE-2023-24531 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-29400 https://www.cve.org/CVERecord?id=CVE-2023-29400 Référence CVE CVE-2023-29402 https://www.cve.org/CVERecord?id=CVE-2023-29402 Référence CVE CVE-2023-29403 https://www.cve.org/CVERecord?id=CVE-2023-29403 Référence CVE CVE-2023-29404 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2023-22049 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-2253 https://www.cve.org/CVERecord?id=CVE-2023-2253 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-24531 https://www.cve.org/CVERecord?id=CVE-2023-24531 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25173 https://www.cve.org/CVERecord?id=CVE-2023-25173 Référence CVE CVE-2023-25193 https://www.cve.org/CVERecord?id=CVE-2023-25193 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-23931 https://www.cve.org/CVERecord?id=CVE-2023-23931 Référence CVE CVE-2023-2426 https://www.cve.org/CVERecord?id=CVE-2023-2426 Référence CVE CVE-2023-24329 https://www.cve.org/CVERecord?id=CVE-2023-24329 Référence CVE CVE-2023-24531 https://www.cve.org/CVERecord?id=CVE-2023-24531 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-24751 https://www.cve.org/CVERecord?id=CVE-2023-24751 Référence CVE CVE-2023-24752 https://www.cve.org/CVERecord?id=CVE-2023-24752 Référence CVE CVE-2023-24754 https://www.cve.org/CVERecord?id=CVE-2023-24754 Référence CVE CVE-2023-24755 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0622Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2023-0466 Référence CVE CVE-2023-1255 https://www.cve.org/CVERecord?id=CVE-2023-1255 Référence CVE CVE-2023-2253 https://www.cve.org/CVERecord?id=CVE-2023-2253 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-24531 https://www.cve.org/CVERecord?id=CVE-2023-24531 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25173 https://www.cve.org/CVERecord?id=CVE-2023-25173 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-27043 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0524Multiples vulnérabilités dans VMware Tanzu

g/CVERecord?id=CVE-2022-49043 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465 Référence CVE CVE-2023-0466 https://www.cve.org/CVERecord?id=CVE-2023-0466 Référence CVE CVE-2023-0996 https://www.cve.org/CVERecord?id=CVE-2023-0996 Référence CVE CVE-2023-1255 https://www.cve.org/CVERecord?id=CVE-2023-1255 Référence CVE CVE-2023-24531 https://www.cve.org/CVERecord?id=CVE-2023-24531 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-2455 https://www.cve.org/CVERecord?id=CVE-2023-2455 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-29383 https://www.cve.org/CVERecord?id=CVE-2023-29383 Référence CVE CVE-2023-29400 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0256Multiples vulnérabilités dans Broadcom VMware Tanzu Greenplum

d?id=CVE-2022-41717 Référence CVE CVE-2022-41720 https://www.cve.org/CVERecord?id=CVE-2022-41720 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2022-41724 https://www.cve.org/CVERecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2023-24531 https://www.cve.org/CVERecord?id=CVE-2023-24531 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-29400 https://www.cve.org/CVERecord?id=CVE-2023-29400 Référence CVE CVE-2023-29402 https://www.cve.org/CVERecord?id=CVE-2023-29402 Référence CVE CVE-2023-29403 https://www.cve.org/CVERecord?id=CVE-2023-29403 Référence CVE CVE-2023-29404 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0145Multiples vulnérabilités dans les produits IBM

d?id=CVE-2023-21968 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-23918 https://www.cve.org/CVERecord?id=CVE-2023-23918 Référence CVE CVE-2023-23919 https://www.cve.org/CVERecord?id=CVE-2023-23919 Référence CVE CVE-2023-23920 https://www.cve.org/CVERecord?id=CVE-2023-23920 Référence CVE CVE-2023-23936 https://www.cve.org/CVERecord?id=CVE-2023-23936 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24534 https://www.cve.org/CVERecord?id=CVE-2023-24534 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-2597 https://www.cve.org/CVERecord?id=CVE-2023-2597 Référence CVE CVE-2023-26048 https://www.cve.org/CVERecord?id=CVE-2023-26048 Référence CVE CVE-2023-26049 https://www.cve.org/CVERecord?id=CVE-2023-26049 Référence CVE CVE-2023-26115 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0484Multiples vulnérabilités dans les produits IBM

VERecord?id=CVE-2023-0266 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0386 https://www.cve.org/CVERecord?id=CVE-2023-0386 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-23934 https://www.cve.org/CVERecord?id=CVE-2023-23934 Référence CVE CVE-2023-24532 https://www.cve.org/CVERecord?id=CVE-2023-24532 Référence CVE CVE-2023-24536 https://www.cve.org/CVERecord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24998 Référence CVE CVE-2023-25577 https://www.cve.org/CVERecord?id=CVE-2023-25577 Référence CVE CVE-2023-25930 https://www.cve.org/CVERecord?id=CVE-2023-25930 Référence CVE CVE-2023-26021 https://www.cve.org/CVERecord?id=CVE-2023-26021 Référence CVE CVE-2023-26022 https://www.cve.org/CVERecord?id=CVE-2023-26022 Référence CVE CVE-2023-27555 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-007072The Go Project の Go における制限またはスロットリング無しのリソースの割り当てに関する脆弱性

The Go Project の Go には、制限またはスロットリング無しのリソースの割り当てに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 6 Apr 2023 · Last source change 13 Feb 2025, 16:44 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-28552
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.19.8; 1.20.0-0 < 1.20.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 1.19.8; 1.20.0-0 < 1.20.3 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-24536 · cve.blacktree.nl