Summary
personnummer/rust vulnerable to Improper Input Validation
This vulnerability was reported to the personnummer team in June 2020. The slow response was due to locked ownership of some of the affected packages, which caused delays to update packages prior to disclosure.
The vulnerability is determined to be low severity.
Workarounds
The issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be
000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not
000x.
For more information
If you have any questions or comments about this advisory:
- Open an issue in Personnummer Meta
- Email us at Personnummer Email
Impact
This vulnerability impacts users who rely on the for last digits of personnummer to be a real personnummer.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue have been patched in all repositories. The following versions should be updated to as soon as possible:
C# 3.0.2
D 3.0.1
Dart 3.0.3
Elixir 3.0.0
Go 3.0.1
Java 3.3.0
JavaScript 3.1.0
Kotlin 1.1.0
Lua 3.0.1
PHP 3.0.2
Perl 3.0.0
Python 3.0.2
Ruby 3.0.1
Rust 3.0.0
Scala 3.0.1
Swift 1.0.1
If you are using any of the earlier packages, please update to latest.
Frequently Asked Questions
- What is GHSA-28R9-PQ4C-WP3C? GHSA-28R9-PQ4C-WP3C is a low-severity security vulnerability in personnummer (rust), affecting versions < 3.0.1. It is fixed in 3.0.1.
- Which versions of personnummer are affected by GHSA-28R9-PQ4C-WP3C? personnummer (rust) versions < 3.0.1 is affected.
- Is there a fix for GHSA-28R9-PQ4C-WP3C? Yes. GHSA-28R9-PQ4C-WP3C is fixed in 3.0.1. Upgrade to this version or later.
- Is GHSA-28R9-PQ4C-WP3C exploitable, and should I be worried? Whether GHSA-28R9-PQ4C-WP3C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-28R9-PQ4C-WP3C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-28R9-PQ4C-WP3C? Upgrade
personnummerto 3.0.1 or later.