CVE-2023-22460
Assigner: GitHub_M
Published: 2023-01-04T14:53:19.877Z
State: PUBLISHED
title: go-ipld-prime json codec may panic if asked to encode bytes
problemTypes: descriptions: cweId: CWE-20
description: CWE-20: Improper Input Validation
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 7.5
baseSeverity: HIGH
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
version: 3.1
affected: vendor: ipld
product: go-ipld-prime
versions: version: < 0.19.0
status: affected
descriptions: value: go-ipld-prime is an implementation of the InterPlanetary Linked Data (IPLD) spec interfaces, a batteries-included codec implementations of IPLD for CBOR and JSON, and tooling for basic operations on IPLD objects. Encoding data which contains a Bytes kind Node will pass a Bytes token to the JSON encoder which will panic as it doesn't expect to receive Bytes tokens. Such an encode should be treated as an error, as plain JSON should not be able to encode Bytes. This only impacts uses of the `json` codec. `dag-json` is not impacted. Use of `json` as a decoder is not impacted. This issue is fixed in v0.19.0. As a workaround, one may prefer the `dag-json` codec, which has the ability to encode bytes.
source: advisory: GHSA-c653-6hhg-9x92
discovery: UNKNOWN