romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-04-14 22:21:41 +03:00
Code Issues Projects Releases Packages Wiki Activity

VULN-DISCLOSURE-POLICY.md: CRLF in data

Browse source 
we reject the idea of *CRLF injection* by the user itself as a general
security problem

Closes #20157
This commit is contained in:
Daniel Stenberg 2026-01-02 10:54:47 +01:00
parent ce423079dc
commit ae1597c312
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/VULN-DISCLOSURE-POLICY.md
View file

@ -354,6 +354,21 @@ using the protocols or options that require the use of those algorithms.
When servers upgrade to use secure alternatives, curl users should use those
options/protocols.
## CRLF in data
curl makes barely any claims of *cleaning* input or rejecting invalid data. A
user that uses a curl feature can send in *creative* sequences that include
carriage-return (CR) or line-feed (LF) characters.
Therefore, we reject the idea of *CRLF injection* as a security problem. It is
a *feature* that users can send creative byte sequences. If users do not want
to send such octets, they are in control and should avoid sending such bytes
to curl.
For example, a user might pass in a username that looks like
`Mr[CR][LF]Smith`. It may cause some minor havoc in the protocol handling,
depending on what protocol is used.
# curl major incident response
Vulnerability disclosure manages the full life cycle of a vulnerability