ZDF
Sign inSign up

Vulnerabilities

Security research · RUSTSEC-2025-0173

can cause an authentication bypass

Published Jun 2, 2025 · RustSec Rust

Last checked Oct 27, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2025-0173. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.

Same product and reporting

Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
RustSec Rust

In affected versions, can return after it gets the username successfully. PAM modules that return this "error" code from or early-return a success code to PAM without doing any further verification. This means a user could log in when they shouldn't be able to (e.g., if the module is ). The macro of this crate early-returns the code in this exact way: The root cause is an [incorrect FFI declaration][ffi-decl] for [ ][pam-get-user]. This C function writes a pointer to the username through its argument (of type ). This crate's binding declared this argument as a shared reference ( ). Writing thr

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix RUSTSEC-2025-0173

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the rustsec record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2025-0173. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 2, 2025 · RustSec Advisory DB

    Detected

    In affected versions, can return after it gets the username successfully. PAM modules that return this "error" code from or early-return a success code to PAM without doing any further verification. This means a user could log in when they shouldn't be able to (e.g., if the module is ). The macro of this crate early-returns the code in this exact way: The root cause is an [incorrect FFI declaratio

Sources

  • RustSec Advisory DBVendor advisoryRUSTSEC-2025-0173

    In affected versions, can return after it gets the username successfully. PAM modules that return this "error" code from or early-return a success code to PAM without doing any further verification. This means a user could log in when they shouldn't be able to (e.g., if the modul

    crates.io

Freshness

Last verified in this catalog Unknown date. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • RustSec Advisory DBOct 27, 2026