# SUSE-SU-2024:4433-1: Security update for govulncheck-vulndb

> This update refreshes the Go vulnerability database to include recent CVEs, ensuring accurate security scanning for Go applications.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2024

## What is SUSE-SU-2024:4433-1?

SUSE-SU-2024:4433-1 is a vulnerability in govulncheck-vulndb, published on 30 Dec 2024. 

### Official description

This update for govulncheck-vulndb fixes the following issues:

- Update to version 0.0.20241218T202206 2024-12-18T20:22:06Z. (jsc#PED-11136)
  Go CVE Numbering Authority IDs added or updated with aliases:
  * GO-2024-3333

- Update to version 0.0.20241218T163557 2024-12-18T16:35:57Z. (jsc#PED-11136)
  Go CVE Numbering Authority IDs added or updated with aliases:
  * GO-2024-3331 GHSA-9j3m-fr7q-jxfw
  * GO-2024-3334 GHSA-qqc8-rv37-79q5
  * GO-2024-3335 GHSA-xx83-cxmq-x89m
  * GO-2024-3336 GHSA-cwq8-g58r-32hg
  * GO-2024-3337 GHSA-69pr-78gv-7c6h
  * GO-2024-3338 GHSA-826h-p4c3-477p
  * GO-2024-3339 GHSA-8wcc-m6j2-qxvm
  * GO-2024-3340 GHSA-v647-h8jj-fw5r

- Update to version 0.0.20241213T205935 2024-12-13T20:59:35Z. (jsc#PED-11136)
  Go CVE Numbering Authority IDs added or updated with aliases:
  * GO-2022-0635 GHSA-7f33-f4f5-xwgw
  * GO-2022-0646 GHSA-f5pg-7wfw-84q9
  * GO-2022-0828 GHSA-fx8w-mjvm-hvpc
  * GO-2023-2170 GHSA-q78c-gwqw-jcmc
  * GO-2023-2330 GHSA-7fxm-f474-hf8w
  * GO-2024-2901 GHSA-8hqg-whrw-pv92
  * GO-2024-3104 GHSA-846m-99qv-67mg
  * GO-2024-3122 GHSA-q3hw-3gm4-w5cr
  * GO-2024-3140 GHSA-xxxw-3j6h-q7h6
  * GO-2024-3169 GHSA-fhqq-8f65-5xfc
  * GO-2024-3186 GHSA-586p-749j-fhwp
  * GO-2024-3205 GHSA-xhr3-wf7j-h255
  * GO-2024-3218 GHSA-mqr9-hjr8-2m9w
  * GO-2024-3245 GHSA-95j2-w8x7-hm88
  * GO-2024-3248 GHSA-p26r-gfgc-c47h
  * GO-2024-3259 GHSA-p7mv-53f2-4cwj
  * GO-2024-3265 GHSA-gppm-hq3p-h4rp
  * GO-2024-3268 GHSA-r864-28pw-8682
  * GO-2024-3279 GHSA-7225-m954-23v7
  * GO-2024-3282 GHSA-r4pg-vg54-wxx4
  * GO-2024-3286 GHSA-27wf-5967-98gx
  * GO-2024-3293
  * GO-2024-3295 GHSA-55v3-xh23-96gh
  * GO-2024-3302 GHSA-px8v-pp82-rcvr
  * GO-2024-3306 GHSA-7mwh-q3xm-qh6p
  * GO-2024-3312 GHSA-4c49-9fpc-hc3v
  * GO-2024-3313 GHSA-jpmc-7p9c-4rxf
  * GO-2024-3314 GHSA-c2xf-9v2r-r2rx
  * GO-2024-3315
  * GO-2024-3319 GHSA-vmg2-r3xv-r3xf
  * GO-2024-3321 GHSA-v778-237x-gjrc
  * GO-2024-3323 GHSA-25w9-wqfq-gwqx
  * GO-2024-3324 GHSA-4pjc-pwgq-q9jp
  * GO-2024-3325 GHSA-c7xh-gjv4-4jgv
  * GO-2024-3326 GHSA-fqj6-whhx-47p7
  * GO-2024-3327 GHSA-xx68-37v4-4596
  * GO-2024-3330 GHSA-7prj-hgx4-2xc3

## Which versions are affected by SUSE-SU-2024:4433-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `govulncheck-vulndb` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 0.0.20241218T202206-150000.1.23.1 |
| `govulncheck-vulndb` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 0.0.20241218T202206-150000.1.23.1 |
| `govulncheck-vulndb` | openSUSE:Leap 15.5 | All versions | 0.0.20241218T202206-150000.1.23.1 |
| `govulncheck-vulndb` | openSUSE:Leap 15.6 | All versions | 0.0.20241218T202206-150000.1.23.1 |

## How do I fix SUSE-SU-2024:4433-1?

Upgrade to a fixed version.

## Is SUSE-SU-2024:4433-1 being exploited?

There is no known exploitation of SUSE-SU-2024:4433-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2024:4433-1 and fix it if it is affected.

What it is: SUSE-SU-2024:4433-1 is a vulnerability in govulncheck-vulndb, published on 30 Dec 2024. 
Exploitation: There is no known exploitation of SUSE-SU-2024:4433-1 in the wild and no public exploit code.

Affected product: govulncheck-vulndb. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/SUSE-SU-2024-4433-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2024-4433-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2024:4433-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2024-4433-1/
Summaries are generated and may contain mistakes; the official description above is the record.