# CVE-2024-24790: Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip > The Go net/netip library incorrectly identifies IPv4-mapped IPv6 addresses, potentially bypassing security checks relying on IP classification. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Jun 2024 - **Updated:** 13 Feb 2025 - **Also known as:** AZL-42386, AZL-42395, AZL-42403, AZL-42409, AZL-79050, AZL-98679, BELL-CVE-2024-24790, BIT-golang-2024-24790, CLSA-2025-1748002217, CLSA-2025-1748638811, DEBIAN-CVE-2024-24790, GHSA-49gw-vxvf-fc2g, GO-2024-2887, MINI-84wj-jc3h-3hj3, MINI-p4fp-8qg2-qgmh, MINI-rfm6-qv6q-cx2x, OESA-2024-1770, RHSA-2024:8876, RLSA-2024:8876, SUSE-SU-2025:0302-1, SUSE-SU-2025:0377-1, UBUNTU-CVE-2024-24790, openSUSE-SU-2024:14077-1, openSUSE-SU-2024:14185-1, openSUSE-SU-2024:14554-1, openSUSE-SU-2025:14723-1 ## What is CVE-2024-24790? CVE-2024-24790 is a critical vulnerability in Golang Go, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms. ## Which versions are affected by CVE-2024-24790? 2 open source packages ship an affected version, including golang and stdlib. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `golang` | Bitnami | All versions | 1.21.11, 1.22.4 | | `stdlib` | Go | All versions | 1.21.11, 1.22.4 | | `delve` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.1-1.module+el8.10.0+22223+9d99ca85 | | `delve-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.1-1.module+el8.10.0+22223+9d99ca85 | | `delve-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.1-1.module+el8.10.0+22223+9d99ca85 | | `go-toolset` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22328+683b6a23 | | `golang` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22325+dc584f75 | | `golang-bin` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22325+dc584f75 | | `golang-docs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22325+dc584f75 | | `golang-misc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22325+dc584f75 | | `golang-src` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22325+dc584f75 | | `golang-tests` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.22.7-1.module+el8.10.0+22325+dc584f75 | | `delve` | Rocky Linux:8 | All versions | 0:1.22.1-1.module+el8.10.0+1879+0cb86608 | | `go-toolset` | Rocky Linux:8 | All versions | 0:1.22.7-1.module+el8.10.0+1879+0cb86608 | | `golang` | Rocky Linux:8 | All versions | 0:1.22.7-1.module+el8.10.0+1879+0cb86608 | | `google-osconfig-agent` | SUSE:Linux Enterprise Micro 5.5 | All versions | 20250115.01-150000.1.41.1 | | `google-osconfig-agent` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 20250115.01-1.32.1 | | `google-osconfig-agent` | SUSE:Linux Enterprise Module for Public Cloud 15 SP3 | All versions | 20250115.01-150000.1.41.1 | | `google-osconfig-agent` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 20250115.01-150000.1.41.1 | | `google-osconfig-agent` | SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | All versions | 20250115.01-150000.1.41.1 | | `google-osconfig-agent` | SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | All versions | 20250115.01-150000.1.41.1 | | `google-osconfig-agent` | openSUSE:Leap 15.6 | All versions | 20250115.01-150000.1.41.1 | | `google-osconfig-agent` | openSUSE:Tumbleweed | All versions | 20250115.01-1.1 | | `helmfile` | openSUSE:Tumbleweed | All versions | 0.166.0-1.1 | | `kubelogin` | openSUSE:Tumbleweed | All versions | 0.1.4-1.1 | | `oras` | openSUSE:Tumbleweed | All versions | 1.2.1-1.1 | Products: Golang Go. ## How do I fix CVE-2024-24790? Upgrade golang to a fixed version for your release line: 1.21.11 or 1.22.4. ## Is CVE-2024-24790 being exploited? There is no known exploitation of CVE-2024-24790 in the wild and no public exploit code. ## Other vulnerabilities in Golang Go - [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild) - [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8) - [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8) - [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8) - [CVE-2023-24538](https://insights.sbomify.com/CVE-2023-24538/): Backticks not treated as string delimiters in html/template (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-24790 and fix it if it is affected. What it is: CVE-2024-24790 is a critical vulnerability in Golang Go, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-24790 in the wild and no public exploit code. Affected packages and fixed versions: - golang (Bitnami): affected all versions; fixed in 1.21.11, 1.22.4 - stdlib (Go): affected all versions; fixed in 1.21.11, 1.22.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-24790/ (Markdown: https://insights.sbomify.com/CVE-2024-24790/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24790 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24790 - OSV: https://osv.dev/vulnerability/CVE-2024-24790 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-24790/ Summaries are generated and may contain mistakes; the official description above is the record.