Skip to content

🔒 Fix loose type comparison vulnerability in Cif.php#211

Merged
ronanguilloux merged 1 commit intomasterfrom
fix/loose-type-comparison-cif-17394091391970110120
Mar 20, 2026
Merged

🔒 Fix loose type comparison vulnerability in Cif.php#211
ronanguilloux merged 1 commit intomasterfrom
fix/loose-type-comparison-cif-17394091391970110120

Conversation

@ronanguilloux
Copy link
Copy Markdown
Owner

🎯 What: Fixed a vulnerability in src/IsoCodes/Cif.php caused by loose type comparison (==) when validating the control digit of a CIF.

⚠️ Risk: Using == instead of === allows unexpected type coercions (type juggling vulnerabilities). For instance, in PHP, string comparisons like "0e123" == "0e456" evaluate to true. If a malformed CIF string evaluated numerically equals the calculated control digit, the validator would incorrectly accept it as valid, potentially bypassing system validations.

🛡️ Solution:

  • Replaced the == operators with strict comparison === operators.
  • Explicitly cast the calculated integer $controlDigit to a string ((string) $controlDigit) before comparing it strictly against $cif[8] (which is a string character).
  • Compared $cif[8] and $cifCodes[$controlDigit] strictly, as both evaluate to string characters.

Tested locally, ran code formatters, and successfully passed the test suite (make tests & make quality).


PR created automatically by Jules for task 17394091391970110120 started by @ronanguilloux

Replaced == with === when comparing control digits in Cif::validate to prevent
unintended type coercions. Casted computed control digit to string where necessary
to match the string type of the character extracted from the CIF string.

Co-authored-by: ronanguilloux <313677+ronanguilloux@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@ronanguilloux ronanguilloux merged commit 489f34f into master Mar 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant