-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulnerability CWE-113 agreementbot/api.go:325 #4208
Labels
Comments
omordyk
added a commit
that referenced
this issue
Dec 16, 2024
Signed-off-by: Oleksandr Mordyk <[email protected]>
12 tasks
12 tasks
omordyk
added a commit
that referenced
this issue
Jan 9, 2025
Signed-off-by: Oleksandr Mordyk <[email protected]>
omordyk
added a commit
that referenced
this issue
Jan 9, 2025
Signed-off-by: Oleksandr Mordyk <[email protected]>
LiilyZhang
pushed a commit
to LiilyZhang/anax
that referenced
this issue
Jan 9, 2025
Signed-off-by: Oleksandr Mordyk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vulnerability CWE-113 agreementbot/api.go:325
http://cwe.mitre.org/data/definitions/113.html
Pr: #4210
Description:
Software places user-controlled input in HTTP headers. An attacker could inject line separators (CR/LF sequences) that could split the response message generated by the software into two messages. The second response is completely under the control of the attacker (intermediate web proxies may cache it), with could produce multiple conditions (web defacement, cache poisoning, cross-site scripting or page hijacking, see CWE-113 for full details). If software needs to generate HTTP headers depending on user-controlled input, such input should be properly neutralized (a white-list validation excluding CR/LF is recommended). Please note that cookies are received and sent in 'Cookie' header in HTTP messages, so if the software generates a Cookie from user input, the input should be properly validated as well.
agreementbot/api.go:325
w.Header().Add("Access-Control-Allow-Origin", r.Header.Get("Origin"))
The text was updated successfully, but these errors were encountered: