Skip to content
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.

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

Add security considerations about injection attacks #307

Merged
merged 1 commit into from
Jan 9, 2023
Merged

Conversation

cabo
Copy link
Member

@cabo cabo commented Nov 17, 2022

No description provided.

These variables need to be translated into the form they take in a
JSONPath query, e.g., by escaping string delimiters, or by only
allowing specific constructs such as `.name` to be formed when the
given values allow that.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't understand this point at all.

values (e.g., by entering them into a Web form).
The resulting class of attacks, *injections* (e.g., SQL injections),
is consistently found among the top causes of application security
vulnerabilities and requires particular attention.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be improved by examples?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am reluctant here. Examples might be used as starting point for potential attackers.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@goessner I understand your reluctance, but the examples are likely to be simple attacks which anyone with the relevant background (attackers, penetration testers, etc.) would think of immediately.

@cabo
Copy link
Member Author

cabo commented Jan 9, 2023

We wanted to add examples, but maybe we can merge this as is. Marking as ready for review.

@cabo cabo marked this pull request as ready for review January 9, 2023 14:20
Copy link
Collaborator

@glyn glyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get this in and polish it later.

@glyn glyn merged commit e76f616 into main Jan 9, 2023
@glyn glyn deleted the injection-warning branch January 9, 2023 18:55
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.

4 participants