CVE-2022-3347 json
Incorrect validation of root DNSSEC public keys in github.com/peterzen/goresolver
published 4y ago modified 4mo ago also GHSA-jr65-gpj5-cw74 , GO-2022-1026 , EUVD-2022-7669
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
DNSSEC validation is not performed correctly. An attacker can cause this package to report successful validation for invalid, attacker-controlled records. Root DNSSEC public keys are not validated, permitting an attacker to present a self-signed root key and delegation chain.
Is CVE-2022-3347 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/peterzen/goresolver | <=1.0.2 all versions |
no fix listed |
Affected products
- github.com/peterzen/goresolver github.com/peterzen/goresolver
Classification
References
-
pkg.go.dev
/vuln/GO-2022-1026
web, vendor-advisory
-
github.com
/peterzen/goresolver/issues/5#issuecomment-1150214257
web, issue-tracking, third-party-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2022-3347
advisory
-
github.com
/peterzen/goresolver
package
Sources
- CVE List CVE-2022-3347
- GitHub Advisory GHSA-jr65-gpj5-cw74
- NVD CVE-2022-3347
- OSV GO-2022-1026
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.