Lucene search
+L
RustSecMost viewed

1333 matches found

RustSec
RustSec
•added 2026/06/18 12:00 p.m.•28 views

Integer overflow in tract-nnef NNEF tensor parser leads to out-of-bounds read on model load

tractnnef::tensors::readtensor builds a tensor shape from attacker-controlled 32-bit dimensions and computes both the element count productshape and the byte allocation productshape sizeofdt with unchecked usize arithmetic. In release builds no overflow-checks both products wrap modulo 2^64. A...

6.1CVSS6.3AI score0.00181EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/03/20 12:00 p.m.•28 views

`tokio-tls` is unmaintained

The tokio-tls crate is unmaintained. It was part of the Tokio 0.1 ecosystem and has been superseded by the main tokio crate...

5.7AI score
SaveExploits0
RustSec
RustSec
•added 2026/03/19 12:00 p.m.•28 views

CRL Distribution Point Scope Check Logic Error in AWS-LC

A logic error in CRL distribution point matching in AWS-LC allows a revoked certificate to bypass revocation checks during certificate validation, when the application enables CRL checking and uses partitioned CRLs with Issuing Distribution Point IDP extensions. Customers of AWS services do not...

9.1CVSS5.9AI score0.00268EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/03/04 12:00 p.m.•28 views

Cache poisoning via insecure-by-default cache key

Pingora versions prior to 0.8.0 generated cache keys using only the URI path, excluding critical factors such as the host header. This allows an attacker to poison the cache and serve cross-origin responses to users. This vulnerability affects users of Pingora's alpha proxy caching feature who...

8.4CVSS6.6AI score0.00221EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/03/04 12:00 p.m.•28 views

Incorrect Check of Signer Response Norm During Verification

The ML-DSA verification algorithm as specified in FIPS 204, subsection 6.3 requires verifiers to check that the infinity norm of the deserialized signer response $z$ does not exceed $\gamma1 - \beta$ line 13 of Algorithm 8. The same check is required to be performed during signature generation...

5.8AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/03/02 12:00 p.m.•28 views

Timing Side-Channel in AES-CCM Tag Verification in AWS-LC

Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis. The impacted implementations are through the EVP CIPHER API: EVPaes128ccm, EVPaes192ccm, and EVPaes256ccm. Customers of AWS servic...

8.2CVSS8.4AI score0.00494EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/03/02 12:00 p.m.•28 views

PKCS7_verify Signature Validation Bypass in AWS-LC

Improper signature validation in PKCS7verify in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes. Customers of AWS services do not need to take action. aws-lc-sys contains code from AWS-LC. Applications using...

8.7CVSS8.3AI score0.00408EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/02/19 12:00 p.m.•28 views

`polymarkets-client-sdk` was removed from crates.io for malicious code

It appeared to be typosquatting existing crate polymarket-client-sdk polymarkets vs polymarket and attempting to steal credentials from local files. The malicious crate had 1 version published on 2026-02-19 an hour before removal and hadn't been downloaded. There were no crates depending on this...

5.4AI score
SaveExploits0
RustSec
RustSec
•added 2025/12/30 12:00 p.m.•28 views

theshit vulnerable to unsafe loading of user-owned Python rules when running as root

The application loads custom Python rules and configuration files from user-writable locations e.g., /.config/theshit/ without validating ownership or permissions when executed with elevated privileges. If the tool is invoked with sudo or otherwise runs with an effective UID of root, it continues...

6.7CVSS6.2AI score0.00134EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2025/11/17 12:00 p.m.•28 views

opentelemetry-jaeger crate is unmaintained

The opentelemetry-jaeger crate is deprecated and no longer actively maintained. The Jaeger propagator implementation has been migrated to opentelemetry-jaeger-propagator. More information and examples of using OTLP with Jaeger can be found in Introducing native support for OpenTelemetry in Jaeger...

6.7AI score
SaveExploits0
RustSec
RustSec
•added 2025/10/21 12:00 p.m.•28 views

Uninitialized memory exposure in any_as_u8_slice

The safe function anyasu8slice can create byte slices that reference uninitialized memory when used with types containing padding bytes. The function uses slice::fromrawparts to create a &u8 covering the entire size of a type, including padding bytes. According to Rust's documentation, fromrawpar...

7.2AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2025/09/08 12:00 p.m.•28 views

servo-fontconfig crate is unmaintained

The servo-fontconfig crate is no longer actively maintained. If you rely on this crate, consider switching to a maintained alternative. Recommended alternatives - fontconfig-rs...

6.9AI score
SaveExploits0
RustSec
RustSec
•added 2025/06/11 12:00 p.m.•28 views

matrix-sdk-crypto vulnerable to encrypted event sender spoofing by homeserver administrator

matrix-sdk-crypto versions 0.8.0 up to and including 0.11.0 does not correctly validate the sender of an encrypted event. Accordingly, a malicious homeserver operator can modify events served to clients, making those events appear to the recipient as if they were sent by another user. Although th...

4.9CVSS7.2AI score0.00369EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2025/06/03 12:00 p.m.•28 views

--allow-read / --allow-write permission bypass in `node:sqlite`

It is possible to bypass Deno's read/write permission checks by using ATTACH DATABASE statement. PoC // poc.js import DatabaseSync from "node:sqlite" const db = new DatabaseSync":memory:"; db.exec"ATTACH DATABASE 'test.db' as test;"; db.exec"CREATE TABLE test.test id INTEGER PRIMARY KEY, name...

9.1CVSS7AI score0.00468EPSS
SaveExploits1Affected Software1
RustSec
RustSec
•added 2025/05/17 12:00 p.m.•28 views

surf is unmaintained

The developer has indicated that the crate is unmaintained. The last release is over three years old from 2021, the crate depends on the deprecated async-std crate and on a very old version of rustls for TLS support. Possible alternatives - reqwest - ureq...

7.2AI score
SaveExploits0
RustSec
RustSec
•added 2025/03/08 12:00 p.m.•28 views

humantime is unmaintained

Latest humantime crates.io release is four years old and GitHub repository has not seen commits in four years. Question about maintenance status has not gotten any reaction from maintainer: https://github.com/tailhook/humantime/issues/31 Update: maintained again The maintainer has responded and...

7.1AI score
SaveExploits0
RustSec
RustSec
•added 2025/03/04 12:00 p.m.•28 views

`backoff` is unmaintained.

The backoff crate is no longer actively maintained. For exponential backoffs/retrying, you can use the backon crate...

7.1AI score
SaveExploits0
RustSec
RustSec
•added 2025/02/15 12:00 p.m.•28 views

`sophosfirewall-python` was removed from crates.io for malicious code

sophosfirewall-python was part of a campaign that attempted to exfiltrate environmental data from the host. The malicious crate had 6 versions published in February 2025, and had no evidence of actual usage. This crate had no dependencies on crates.io...

5.9AI score
SaveExploits0
RustSec
RustSec
•added 2025/01/30 12:00 p.m.•28 views

`custom-req-on-workers` was removed from crates.io for malicious code

custom-req-on-workers was part of a campaign that attempted to exfiltrate environmental data from the host. The malicious crate had 1 version published in January 2025, and had no evidence of actual usage. This crate had no dependencies on crates.io...

5.9AI score
SaveExploits0
RustSec
RustSec
•added 2024/08/27 12:00 p.m.•28 views

CWA-2023-004: Excessive number of function parameters in compiled Wasm

A specifically crafted Wasm file can cause the VM to consume excessive amounts of memory when compiling a contract. This can lead to high memory usage, slowdowns, potentially a crash and can poison a lock in the VM, preventing any further interaction with contracts. For more information, see...

7AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2023/03/14 12:00 p.m.•28 views

Gitoxide has renamed its crates.

All crates in the gitoxide project have been renamed from git- to gix-. The git- prefixed crates are no longer being updated. Switch to using gix-hash to continue receiving updates...

6.8AI score
SaveExploits0
RustSec
RustSec
•added 2023/02/20 12:00 p.m.•28 views

Possible out-of-bounds read in release mode

Affected versions of this crate were using a debug assertion to validate the last parameter of partialsort. This would allow invalid inputs to cause an out-of-bounds read instead of immediately panicking, when compiled without debug assertions. All writes are bounds-checked, so the out-of-bounds...

4.8AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2022/12/04 12:00 p.m.•28 views

`claim` is Unmaintained

The last release was in February 2021, almost two years ago. The maintainer has been unresponsive regarding this crate for over a year. A pending issue with claim's dependencies has made the crate difficult to use. Possible Alternatives The below list has not been vetted in any way and may or may...

3.5AI score
SaveExploits0
RustSec
RustSec
•added 2022/08/26 12:00 p.m.•28 views

`os_socketaddr` invalidly assumes the memory layout of std::net::SocketAddr

The ossocketaddr crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. These layout were changed into idiomatic rust...

2.4AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2022/08/15 12:00 p.m.•28 views

Use after free in MacOS / iOS implementation

In iana-time-zone v0.1.43 a use-after-free bug in the MacOS / iOS implementation was introduced. The copied system time zone was released before its name was copied. If the system time zone was changed between the call of CFRelease and str::toowned, random memory would be copied...

1.4AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2022/01/26 12:00 p.m.•28 views

xml-rs is Unmaintained

xml-rs is a XML parser has open issues around parsing including integer overflows / panics that may or may not be an issue with untrusted data. Together with these open issues with Unmaintained status xml-rs may or may not be suited to parse untrusted data. Alternatives - quick-xml...

5.1AI score
SaveExploits0
RustSec
RustSec
•added 2022/01/17 12:00 p.m.•28 views

`markdown` (1.0.0 and higher) is maintained

A new markdown crate has been brought over by a new maintainer replacing the old crate. The crate GitHub repository is now wooorm/markdown-rs This advisory has been withdraw since version 1.0.0 was released on 2025-04-23. markdown 0.3.0 and lower was unmaintained The old markdown crate was no...

7.2AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2021/12/24 12:00 p.m.•28 views

dotenv is Unmaintained

dotenv by description is meant to be used in development or testing only. Using this in production may or may not be advisable. Alternatives The below may or may not be feasible alternatives: - dotenvy...

1.7AI score
SaveExploits0
RustSec
RustSec
•added 2021/12/21 12:00 p.m.•28 views

Use after free in lru crate

Lru crate has use after free vulnerability. Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop, will remove and free the value, and but it's still possible to access the reference of value which is already...

7.5CVSS3AI score0.01219EPSS
SaveExploits1Affected Software1
RustSec
RustSec
•added 2021/10/08 12:00 p.m.•28 views

Non-aligned u32 read in Chacha20 encryption and decryption

The implementation does not enforce alignment requirements on input slices while incorrectly assuming 4-byte alignment through an unsafe call to std::slice::fromrawpartsmut, which breaks the contract and introduces undefined behavior. This affects Chacha20 encryption and decryption in crypto2...

9.8CVSS2.1AI score0.00778EPSS
SaveExploits0
RustSec
RustSec
•added 2021/08/18 12:00 p.m.•28 views

ansi_term is Unmaintained

The maintainer has advised that this crate is deprecated and will not receive any maintenance. The crate does not seem to have much dependencies and may or may not be ok to use as-is. Last release seems to have been three years ago. Possible Alternatives The below list has not been vetted in any...

7.2AI score
SaveExploits0
RustSec
RustSec
•added 2021/07/25 12:00 p.m.•28 views

Process crashes when the cell used as DepGroup is not alive

It's easy to create a malign transaction which uses the dead cell as the DepGroup in the DepCells. The transaction can crash all the receiving nodes...

7.8CVSS2AI score0.01124EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2021/07/07 12:00 p.m.•28 views

Lenient `hyper` header parsing of `Content-Length` could allow request smuggling

hyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers. Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error. To be vulnerable, hyper must be used as an HTTP/1 server and using ...

5.3CVSS0.3AI score0.01126EPSS
SaveExploits1Affected Software1
RustSec
RustSec
•added 2021/05/20 12:00 p.m.•28 views

Crate `twoway` deprecated by the author

The commit e99b3c7 releasing version 0.2.2 explicitly deprecates twoway in favour of memchr crate...

3.7AI score
SaveExploits0
RustSec
RustSec
•added 2021/04/29 12:00 p.m.•28 views

`aes-ctr` has been merged into the `aes` crate

Please use the aes crate going forward. The new repository location is at: The aes crate now has an optional ctr feature which autodetects SIMD features on i686/x86-64 targets and uses them if available, or otherwise falls back to the implementation in the ctr crate. If you would prefer not to ha...

SaveExploits0
RustSec
RustSec
•added 2021/02/05 12:00 p.m.•28 views

Multiple Transfer-Encoding headers misinterprets request payload

hyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can...

8.1CVSS1.4AI score0.04732EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2020/12/20 12:00 p.m.•28 views

Soundness issue: Input<R> can be misused to create data race to an object

Input implements Send without requiring R: Send. Affected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption. The flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of...

5.9CVSS2.8AI score0.01079EPSS
SaveExploits1Affected Software1
RustSec
RustSec
•added 2020/11/15 12:00 p.m.•28 views

CopyCell lacks bounds on its Send trait allowing for data races

CopyCell is a Cell-like type that is implemented for any type T that is Copyable. It's Send trait has no bounds on the contained type. As not all Copyable types are thread safe, for example non-mutable references implement the Copy trait, it is possible to send references to types with interior...

8.1CVSS2.3AI score0.01098EPSS
SaveExploits1
RustSec
RustSec
•added 2020/11/02 12:00 p.m.•28 views

crate has been renamed to `qp2p`

This crate has been renamed from quic-p2p to qp2p. The new repository location is:...

6.9AI score
SaveExploits0
RustSec
RustSec
•added 2020/10/01 12:00 p.m.•28 views

Obsolete versions of the `rustsec` crate do not support the new V3 advisory format

If you are seeing this message, you are running an obsolete version of cargo-audit which does not support the new V3 advisory format. These versions are end-of-life. This advisory is a notice that that it will soon be unable to parse the advisory database. Please upgrade cargo-audit to a newer...

2.7AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2020/01/20 12:00 p.m.•28 views

rust_sodium is unmaintained; switch to a modern alternative

The rustsodium crate is no longer maintained by its current owner, who advise in the repository readme that they are looking for someone else to take ownership of it. We recommend you switch to an alternative crate such as: - sodiumoxide...

3.3AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2019/06/20 12:00 p.m.•28 views

`boxfnonce` obsolete with release of Rust 1.35.0

This commit marks the boxfnonce crate as obsolete and the GitHub repo has since been archived. The functionality of boxfnonce has been added to Rust since 1.35.0. Use Box...

1.1AI score
SaveExploits0
RustSec
RustSec
•added 2018/12/18 12:00 p.m.•28 views

Enum repr causing potential memory corruption

The attribute repr added to enums to be compatible with C-FFI caused memory corruption on MSVC toolchain. arrayfire crates = version 3.5.0 do not have this issue when used with Rust versions 1.27 or earlier. The issue only started to appear since Rust version 1.28. The issue seems to be interlink...

9.8CVSS5.6AI score0.01658EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2018/06/30 12:00 p.m.•28 views

quickersort is deprecated and unmaintained

The author of the quickersort crate has deprecated it and does not recommend using it anymore. Everything in it has been incorporated into std::sortunstable in the standard library as of Rust 1.20. std::sortunstable: https://doc.rust-lang.org/stable/std/primitive.slice.htmlmethod.sortunstable...

4.3AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2018/06/21 12:00 p.m.•28 views

An integer underflow could lead to panic

A mistake in error handling in untrusted before 0.6.2 could lead to an integer underflow and panic if a user of the crate didn't properly check for errors returned by untrusted. Combination of these two programming errors one in untrusted and another by user of this crate could lead to a panic an...

7.5CVSS3AI score0.01411EPSS
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/08/04 12:00 p.m.•27 views

Double free / use-after-free in `ReadChunk::commit` when an element's `Drop` panics

ReadChunk::commit and ReadChunk::commitall drop the committed elements before advancing the consumer head. If an element's Drop panics during the drop loop, head is never advanced, so the ring buffer still treats those slots as holding live elements. When the RingBuffer is later dropped it walks...

6AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/08/03 12:00 p.m.•27 views

`nostr-relay-builder` is unmaintained

The nostr-relay-builder crate is no longer actively maintained as a standalone crate. Its functionality has been incorporated into nostr-sdk starting with version 0.45.0. Users should migrate to nostr-sdk...

5.2AI score
SaveExploits0
RustSec
RustSec
•added 2026/08/01 12:00 p.m.•27 views

Wallet event parsers accept unauthenticated events

The NIP-47 response and notification parsers and the NIP-60 wallet event parsers decrypted relay-provided events before verifying their kind, computed event ID, signature, and expected wallet public key. The decryption peer was derived from the untrusted event author, so successful decryption did...

5.5AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/08/01 12:00 p.m.•27 views

NIP-04 parsing amplifies malformed ciphertext memory use

The NIP-04 decryption parser split attacker-controlled content on every ?iv= separator and collected all resulting segments before checking that the message had the expected two parts. It also Base64-decoded the complete IV text before checking that it represented the required 16-byte AES-CBC IV....

5.5AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/07/06 12:00 p.m.•27 views

Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid

Affected versions of fmt::Display dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with Atomic::null or Shared::null. fmt::Debug impls and pre-0.9 fmt::Display impls, which do not dereference pointers, are not affected by this issue...

6.1AI score
SaveExploits0Affected Software1
Total number of security vulnerabilities1333