nostr-sdk is vulnerable to Improper Verification of Data Authenticity
75
High Risk
The relay pool passes events received from a relay through admission-policy and database paths before confirming that the serialized fields match the claimed event id and signature, and a database result for the claimed id can cause verification to be skipped. The verification cache also keys successful checks by a 64-bit hash rather than the full event id. A malicious relay can send an event whose claimed id matches a known database entry while its content, tags, author, or signature differ, so a forged event reaches policy callbacks or other processing as authentic, with a cache-key collision offering a second bypass path. The fix verifies each event before policy evaluation, database lookup, or propagation and stores the complete event id in the verification cache.
You are affected if you are using a version that falls within the vulnerable range and your application processes or persists events received from untrusted relays.
nostr-sdk is vulnerable to Improper Verification of Data Authenticity in versions 0.0.1 - 0.44.7.
Upgrade the org.rust-nostr:nostr-sdk, org.rust-nostr:nostr-sdk-jvm, or org.rust-nostr:nostr-sdk-kmp library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant