CVE-2022-39213

Go-CVSS has Out-of-bounds Read vulnerability in ParseVector function

package main

import (
	"log"

	gocvss20 "github.com/pandatix/go-cvss/20"
)

func main() {
	_, err := gocvss20.ParseVector("AV:N/AC:L/Au:N/C:P/I:P/A:C/E:U/RL:OF/RC:C/CDP:MH/TD:H/CR:M/IR:M/AR:M")
	if err != nil {
		log.Fatal(err)
	}
}

panic: runtime error: index out of range [3] with length 3

goroutine 1 [running]:
github.com/pandatix/go-cvss/20.ParseVector({0x4aed6c?, 0x0?})
        /home/lucas/go/pkg/mod/github.com/pandatix/[email protected]/20/cvss20.go:54 +0x578
main.main()
        /media/lucas/HDD-K/Documents/cve-2022-xxxxx/main.go:10 +0x25
exit status 2

When a full CVSS v2.0 vector string is parsed using ParseVector, an Out-of-Bounds Read is possible due to a lack of tests. The Go module will then panic.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2022-39213 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem is patched in tag v0.4.0, by the commit d9d478ff0c13b8b09ace030db9262f3c2fe031f4.

1. What is CVE-2022-39213? CVE-2022-39213 is a high-severity out-of-bounds read vulnerability in github.com/pandatix/go-cvss (go), affecting versions >= 0.2.0, < 0.4.0. It is fixed in 0.4.0. A read operation accesses a memory location beyond the intended buffer boundary.
2. How severe is CVE-2022-39213? CVE-2022-39213 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/pandatix/go-cvss are affected by CVE-2022-39213? github.com/pandatix/go-cvss (go) versions >= 0.2.0, < 0.4.0 is affected.
4. Is there a fix for CVE-2022-39213? Yes. CVE-2022-39213 is fixed in 0.4.0. Upgrade to this version or later.
5. Is CVE-2022-39213 exploitable, and should I be worried? Whether CVE-2022-39213 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-39213 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-39213? Upgrade github.com/pandatix/go-cvss to 0.4.0 or later.