Skip to content

Clarify security classification for unsanitized args #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iluuu1994 merged 2 commits into from
May 7, 2026
+3 −2
Merged

Clarify security classification for unsanitized args #30

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b32be9
Clarify security classification for unsanitized args
iluuu1994 Apr 27, 2026
9a509cb
Apply suggestion from Tim
iluuu1994 May 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions security-classification.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,9 @@ We do not classify as a security issue any issue that:
- requires invocation of specific code, which may be valid but is obviously
malicious

- requires invocation of functions with specific arguments, which may be valid
but are obviously malicious
- requires passing malicious arguments to functions clearly not intended to
receive unsanitized values, e.g. mysqli_query(). escapeshellarg() on the
other hand should clearly be hardened against unsafe inputs.

- requires specific actions to be performed on the server, which are not
commonly performed, or are not commonly permissible for the user (uid)
Expand Down