3.3.4, Require __Http- or __Host-Http- prefix for HttpOnly cookies when applicable
Open
Nobody has claimed this yet.
1) Discussion ongoing
V3 (prev V50)
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
Currently, we have this requirement:
| # | Description | Level |
|---|---|---|
| 3.3.4 | Verify that if the value of a cookie is not meant to be accessible to client-side scripts (such as a session token), the cookie must have the 'HttpOnly' attribute set and the same value (e. g. session token) must only be transferred to the client via the 'Set-Cookie' header field. | 2 |
There are apparently new __Http- and __Host-Http- prefixes for HttpOnly cookies, which protects the cookie from being overwritten by client-side JS code. Shall we require this usage somehow in this requirement?
Caveat: there is no __Secure-Http- prefix for some reason.
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
Start with requirement 3.3.4 and the issue's discussion of the __Http- and __Host-Http- cookie prefixes. Determine whether and how those prefixes should apply, including the caveat about __Secure-Http-. Done means the requirement wording and level clearly state the resulting policy.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100