CVE-2023-22963
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe personnummer implementation before 3.0.3 for Dart mishandles numbers in which the last four digits match the ^000[0-9]$ regular expression.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe personnummer Dart library before version 3.0.3 contains a validation flaw where Swedish personal identification numbers ending with digits matching the regex ^000[0-9]$ (i.e., 0000-0009) are incorrectly processed. This likely causes false negatives (valid numbers rejected) or false positives (invalid numbers accepted) in the validation logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate personnummer package usageSearch for personnummer in your project dependencies: check pubspec.yaml or pubspec.lock files for a Dart/Flutter project, or inspect your pub cache if using system-wide installationAffected if The personnummer package is listed as a dependency
-
Determine installed versionRead the version number from pubspec.lock in the personnummer entry, or run 'dart pub deps -- package:personnummer' to see the resolved versionAffected if Version is present and less than 3.0.3
-
Check for validation of 0000-0009 endingsReview your code or tests that call the validation function with Swedish personal numbers ending in 0000 through 0009 (e.g., format YYYYMMDD-XXXX where XXXX matches 0000-0009)Affected if Your application validates or processes Swedish personnummer values and the library version is below 3.0.3
-
Verify validation behaviorTest the validation function with a known valid Swedish personnummer that ends in 0000-0009 and observe whether it is incorrectly rejected (false negative) or if invalid equivalents are incorrectly accepted (false positive)Affected if Validation returns unexpected results for numbers in the 0000-0009 range
You are affected if your project uses the personnummer Dart library at a version lower than 3.0.3 and your application validates Swedish personal identification numbers ending with digits 0000 through 0009.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.3
Upgrade the personnummer Dart package to version 3.0.3 or later to obtain the corrected validation logic.
3.0.3
- Update the personnummer dependency in your pubspec.yaml file to version 3.0.3 or later: personnummer: ^3.0.3
- Run 'dart pub get' or 'flutter pub get' to fetch the updated package version
- Verify the update was successful by checking that personnummer version 3.0.3 or higher is installed
- Rebuild and test your application to ensure the package functions correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22963 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data