OWASP/wstg

Add Testing for Deserialisation of Untrusted Data

Closed

#7 opened on Jun 15, 2017

View on GitHubContributor guide
 (34 comments) (0 reactions) (1 assignee) (1,624 forks)github user discovery
good first issuenew

Repository metrics

Stars
 (9,439 stars)
PR merge metrics
 (Avg merge 24d 19h) (22 merged PRs in 30d)

Description

Contributor guide

Research direction
Review CWE 502 and existing testing structure in the WSTG, then draft a testing procedure for deserialization of untrusted data.
Tech stack
None
Domain
security
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Understanding of deserialization vulnerabilitiesFamiliarity with OWASP WSTG structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55