Clarification: 1.5.1"and"
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
Verify that the application configures XML parsers to use a restrictive
configuration and that unsafe features such as resolving external entities are
disabled to prevent XML eXternal Entity (XXE) attacks.
The "and" makes it sound like they are two separate things, but in reality, "unsafe features" are part of the "restrictive configuration" as far as I know, because implementers cannot achieve a restrictive configuration without dealing with unsafe features. The requirement wording is not technically incorrect, but it is redundant and potentially misleading. The requirement also does not cover the critical aspects of XXE. In simple words, this is a weak requirement.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the requirement in the raw Markdown files under the 5.0/en tree, using the quoted XML parser and XXE wording as the search terms. Review the requirement's wording and surrounding context; it is done when the text clearly and accurately describes restrictive XML parser configuration and the relevant XXE protections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100