GHSA-4XH4-V2PQ-JVHM
Vulnerability from github – Published: 2022-09-19 22:47 – Updated: 2023-01-11 18:59This 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": [
{
"package": {
"ecosystem": "Pub",
"name": "personnummer"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-22963"
],
"database_specific": {
"cwe_ids": [
"CWE-20"
],
"github_reviewed": true,
"github_reviewed_at": "2022-09-19T22:47:29Z",
"nvd_published_at": null,
"severity": "LOW"
},
"details": "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.\n\nThe vulnerability is determined to be low severity.\n\n### Impact\n\nThis vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer. \n\n### Patches\n\nThe issue have been patched in all repositories. The following versions should be updated to as soon as possible:\n\n[C#](https://github.com/advisories/GHSA-qv8q-v995-72gr) 3.0.2 \nD 3.0.1 \n[Dart](https://github.com/advisories/GHSA-4xh4-v2pq-jvhm) 3.0.3 \nElixir 3.0.0 \n[Go](https://github.com/advisories/GHSA-hv53-vf5m-8q94) 3.0.1 \n[Java](https://github.com/advisories/GHSA-q3vw-4jx3-rrr2) 3.3.0 \n[JavaScript](https://github.com/advisories/GHSA-vpgc-7h78-gx8f) 3.1.0 \nKotlin 1.1.0 \nLua 3.0.1 \n[PHP](https://github.com/advisories/GHSA-2p6g-gjp8-ggg9) 3.0.2 \nPerl 3.0.0 \n[Python](https://github.com/advisories/GHSA-rxq3-5249-8hgg) 3.0.2 \n[Ruby](https://github.com/advisories/GHSA-vp9c-fpxx-744v) 3.0.1 \n[Rust](https://github.com/advisories/GHSA-28r9-pq4c-wp3c) 3.0.0 \nScala 3.0.1 \nSwift 1.0.1 \n\nIf you are using any of the earlier packages, please update to latest.\n\n### Workarounds\n\nThe issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be\n000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it\u0027s not\n000x.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)\n* Email us at [Personnummer Email](mailto:security@personnummer.dev)",
"id": "GHSA-4xh4-v2pq-jvhm",
"modified": "2023-01-11T18:59:09Z",
"published": "2022-09-19T22:47:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/personnummer/dart/security/advisories/GHSA-4xh4-v2pq-jvhm"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-22963"
},
{
"type": "PACKAGE",
"url": "https://github.com/personnummer/dart"
},
{
"type": "WEB",
"url": "https://pub.dev/packages/personnummer"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "personnummer/dart vulnerable to Improper Input Validation"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.