Fix incorrect PESEL checksum validation in PlPeselRecognizer #1520
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Description
The PESEL checksum validation in
PlPeselRecognizer.validate_result()
is incorrect. The current implementation does not correctly compute the control digit, leading to false negatives, where valid PESEL numbers are incorrectly rejected.This affects Presidio's ability to correctly recognize and validate PESEL numbers, impacting anonymization and sensitive data detection.
To Reproduce
Run the following test:
**Note if unsure, check this: https://kalkulatory.gofin.pl/kalkulatory/sprawdzanie-pesel-weryfikacja-pesel
Observed Behavior
False
for a valid PESEL due to incorrect checksum computation.Expected Behavior
True
.Root Cause: Incorrect Checksum Calculation
The issue lies in the final checksum validation step. The existing code:
This incorrectly compares
checksum
directly to the last digit of PESEL instead of computing the correct control digit.Proposed Fix
The correct formula to compute the PESEL checksum is:
Why This Fix Works
Additional Context