personnummer/ruby vulnerable to Improper Input ValidationGHSA-vp9c-fpxx-744v
GHSA-vp9c-fpxx-744v is a security vulnerability in personnummer. A fix is available for personnummer — see the affected versions and patch details below.
Real-World Exposure
personnummerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
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.
Impact
This vulnerability impacts users who rely on the for last digits of personnummer to be a real personnummer.
Patches
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.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | personnummer | all versions | 3.0.1bundle update personnummer --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for personnummer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update personnummer to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vp9c-fpxx-744v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-vp9c-fpxx-744v in your dependencies?
Find it across RubyGems, including transitive dependencies.