zaproxy/zaproxy

Insecure deserialization active scanner

Open

#4,112 opened on Dec 4, 2017

View on GitHub
 (17 comments) (0 reactions) (1 assignee)Java (11,922 stars) (2,174 forks)batch import
HacktoberFestIdealFirstBugadd-onenhancementgood first issue

Description

As already discussed in #3883, this is now part of the new Top 10 - A8. Could be cool to add such an active scan rule - based on this tool could be a good start for .NET...

Contributor guide

Tech stack
java
Domain
securitybackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Java developmentfamiliarity with deserialization vulnerabilitiesZAP add on structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Review the discussion in issue #3883 for context on the need for an insecure deserialization scanner. Examine existing active scan rules in the ZAP repository (e.g., in the zap extensions repo) to understand the pattern for implementing a new rule. The issue suggests basing the rule on ysoserial.net; investigate how to adapt similar payload generation for Java/.NET. Consider the assignee's comments for direction. Files to explore: active scan rule implementations in zap extensions, the main ZAP codebase for scanner interfaces.