# GHSA-hv53-vf5m-8q94: personnummer/go vulnerable to Improper Input Validation

> The Go personnummer library incorrectly validates Swedish personal identity numbers, allowing invalid formats to pass validation checks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Feb 2022

## What is GHSA-hv53-vf5m-8q94?

GHSA-hv53-vf5m-8q94 is a vulnerability in github.com/personnummer/go, published on 11 Feb 2022. 

### Official 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#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2  
D 3.0.1  
[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3  
Elixir 3.0.0  
[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1  
[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0  
[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0  
Kotlin 1.1.0  
Lua 3.0.1  
[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2  
Perl 3.0.0  
[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2  
[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1  
[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 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](https://github.com/personnummer/meta/issues)
* Email us at [Personnummer Email](mailto:security@personnummer.dev)

## Which versions are affected by GHSA-hv53-vf5m-8q94?

2 open source packages ship an affected version, including github.com/personnummer/go.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/personnummer/go` | Go | All versions | 3.0.1 |
| `github.com/personnummer/go` | Go | All versions | 3.0.1 |

## How do I fix GHSA-hv53-vf5m-8q94?

Upgrade github.com/personnummer/go to 3.0.1 or later.

## Is GHSA-hv53-vf5m-8q94 being exploited?

There is no known exploitation of GHSA-hv53-vf5m-8q94 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hv53-vf5m-8q94 and fix it if it is affected.

What it is: GHSA-hv53-vf5m-8q94 is a vulnerability in github.com/personnummer/go, published on 11 Feb 2022. 
Exploitation: There is no known exploitation of GHSA-hv53-vf5m-8q94 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/personnummer/go (Go): affected all versions; fixed in 3.0.1
- github.com/personnummer/go (Go): affected all versions; fixed in 3.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-hv53-vf5m-8q94/ (Markdown: https://insights.sbomify.com/GHSA-hv53-vf5m-8q94/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hv53-vf5m-8q94

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hv53-vf5m-8q94/
Summaries are generated and may contain mistakes; the official description above is the record.