feat(942450): add another hex + binary declaration pattern#4374
Merged
Conversation
Contributor
|
📊 Quantitative test results for language: |
dkegel-fastly
approved these changes
Dec 22, 2025
dkegel-fastly
left a comment
There was a problem hiding this comment.
The attacks in the tests look good and dangerous to me
I don't read seclang well, so no opinion about the rest
fzipi
reviewed
Jan 24, 2026
Member
|
Thanks for this update. If you apply my suggestion, I can approve. |
Co-authored-by: Felipe Zipitría <3012076+fzipi@users.noreply.github.com>
Contributor
Author
|
@fzipi it's done. Thanks you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello,
Here is another form of hex declaration that I think 942450 should trigger.
Another PR will come for this payload - which is not handled by PL1 currently:
In a more aggressive form, these SQL injections are particularly dangerous because they allow attackers to design payloads that blindly self-adapt to any random database prefix - a makeshift protection often used by CMS platforms to reduce the impact of SQL injection vulnerabilities:
These injections are currently causing serious harm to the PHP e-commerce ecosystem.
--
What do you think ?
Vincent