23 matches found
MAL-2026-15489 Malicious code in borsh-lite (npm)
--- -= Per source details. Do not edit below this line.=- Source: amazon-inspector eed0e447cd98b9470a197c1dd9b341e6a93ea6f39088f4f93335979827f707b8 The package was found to contain malicious code or consuming dependency that contains malicious code Source: ghsa-malware...
Malware in borsh-lite
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outsid...
Malicious code in borsh-lite (npm)
--- -= Per source details. Do not edit below this line.=- Source: amazon-inspector eed0e447cd98b9470a197c1dd9b341e6a93ea6f39088f4f93335979827f707b8 The package was found to contain malicious code or consuming dependency that contains malicious code Source: ghsa-malware...
Malicious Package
Overview borsh-lite is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship...
WS-2023-0096
Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...
MAL-2025-168 Malicious code in borsh-js (npm)
--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 51f002385b3c94048b1a161d8afd15fab61c24c5e54a4a23d9020a22313bd3f3 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...
Malware in borsh-js
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outsid...
Malicious code in borsh-js (npm)
--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 51f002385b3c94048b1a161d8afd15fab61c24c5e54a4a23d9020a22313bd3f3 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...
Borsh serialization of HashMap is non-canonical
The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding. This can result in consensus splits and cause equivalent objects to be considered...
GHSA-WWQ9-3CPR-MM53 Borsh serialization of HashMap is non-canonical
The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding. This can result in consensus splits and cause equivalent objects to be considered...
RUSTSEC-2024-0402 Borsh serialization of HashMap is non-canonical
The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding. This can result in consensus splits and cause equivalent objects to be considered...
Borsh serialization of HashMap is non-canonical
The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding. This can result in consensus splits and cause equivalent objects to be considered...
PT-2024-40947 · Softwarex · Softwarex
Name of the Vulnerable Software and Affected Versions: SoftwareX versions prior to 0.15.1 Description: The issue concerns the borsh serialization of the HashMap, which did not adhere to the borsh specification. This led to potential non-canonical encodings that depended on the insertion order, an...
accountnovafi (>=0.1.0, <=0.2.0), accountnovafi1 (0.1.0) +641 more potentially affected by unknown CVE via borsh (>=0.2.10, <=0.10.4)
borsh CARGO version =0.2.10, =0.1.0, =0.1.0, =0.0.1-dev.10, =1.0.5, =0.0.1, =0.0.1, =0.1.0, =0.0.1, =0.1.0, =0.1.0, =0.1.1 and more Source cves: unknown CVE Source advisory: OSV:GHSA-FJX5-QPF4-XJF2...
GHSA-FJX5-QPF4-XJF2 Parsing borsh messages with ZST which are not-copy/clone is unsound
Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...
accountnovafi (>=0.1.0, <=0.2.0), accountnovafi1 (0.1.0) +602 more potentially affected by unknown CVE via borsh (>=0.2.10, <=0.10.3)
borsh CARGO version =0.2.10, =0.1.0, =0.1.0, =1.0.5, =0.0.1, =0.0.1, =0.1.0, =0.0.1, =0.1.0, =0.1.0, =0.3.0, =0.3.1 and more Source cves: unknown CVE Source advisory: GHSA-FJX5-QPF4-XJF2...
Parsing borsh messages with ZST which are not-copy/clone is unsound
Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...
RUSTSEC-2023-0033 Parsing borsh messages with ZST which are not-copy/clone is unsound
Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...
Parsing borsh messages with ZST which are not-copy/clone is unsound
Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...
accountnovafi (>=0.1.0, <=0.2.0), accountnovafi1 (0.1.0) +602 more potentially affected by unknown CVE via borsh (>=0.2.10, <=0.10.3)
borsh CARGO version =0.2.10, =0.1.0, =0.1.0, =1.0.5, =0.0.1, =0.0.1, =0.1.0, =0.0.1, =0.1.0, =0.1.0, =0.3.0, =0.3.1 and more Source cves: unknown CVE Source advisory: OSV:RUSTSEC-2023-0033...