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.

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

Jump to bottom

feat(JS rules): add express rule around unsafe deserialization #630

Merged
merged 1 commit into from
Feb 21, 2023
Merged

feat(JS rules): add express rule around unsafe deserialization #630

merged 1 commit into from
Feb 21, 2023

Conversation

elsapet
Copy link
Contributor

@elsapet elsapet commented Feb 21, 2023 •
edited
Loading

Description

Add JS express rule to trigger if we try to deserialize something straight from the request data. We cover two serialization libraries:

Relates to #606

Checklist

  • I've added test coverage that shows my fix or feature works as expected.
  • I've updated or added documentation if required.
  • I've included usage information in the description if CLI behavior was updated or added.
  • PR title follows Conventional Commits format

@elsapet elsapet force-pushed the feat/javascript-cwe-502-unsafe-deserialization branch from 6083def to 4f8c31e Compare February 21, 2023 10:25
@elsapet elsapet merged commit 57f5d02 into main Feb 21, 2023
@elsapet elsapet deleted the feat/javascript-cwe-502-unsafe-deserialization branch February 21, 2023 15:57
@elsapet elsapet mentioned this pull request Feb 22, 2023
Closed
26 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vjerci vjerci vjerci approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elsapet @vjerci