← Back to results
Vulnerability record · public intelligence
CVE-2022-23495
HIGH

go-merkledag's ProtoNode may be modified such that common method calls may panic

Published Dec 8, 2022 · Updated Nov 3, 2026

Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood1.38%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

go-merkledag's ProtoNode may be modified such that common method calls may panic

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A `ProtoNode` may be modified in such a way as to cause various encode errors which will trigger a panic on common method calls that don't allow for error returns.

Potential impact

A ProtoNode may be modified in such a way as to cause various encode errors which will trigger a panic on common method calls that don't allow for error returns. A ProtoNode should only be able to encode to valid DAG-PB, attempting to encode invalid DAG-PB forms will result in an error from the codec. Manipulation of an existing (newly created or decoded) ProtoNode using the modifier methods did not account for certain states that would place the ProtoNode into an unencodeable form. Due to conformance with the github.com/ipfs/go-block-formatBlock and github.com/ipfs/go-ipld-formatNode interfaces, certain methods, which internally require a re-encode if state has changed, will panic due to the inability to return an error. Additionally, use of the ProtoNodeSetCidBuilder() method to set a non-functioning CidBuilder (such as one that refers to a multihash where an implementation of that hash function is not available) may cause the same methods to panic as a new CID is required but cannot be created.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Source repository ↗
  5. Source repository ↗
  6. Source repository ↗
  7. https://en.wikipedia.org/wiki/Directed_acyclic_graph ↗
  8. Source repository ↗
  9. Source repository ↗

Record history

Published Dec 8, 2022 · Last refreshed Nov 3, 2026