You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
header := ctx.GetHeader("Authorization")
if header == "" {
ctx.JSON(http.StatusUnauthorized, models.ResponseJson{
Success: false,
Message: "authorization is required",
})
ctx.Abort()
return
}
parts := strings.Split(header, " ")
fmt.Println(parts)
In line 28 of the middleware/jwt_refresh_token_middleware.go file, the program uses fmt.Println(parts) to print the split header (the value obtained from the Authorization header). This is a potential security risk because if the value is controlled by the user (which appears to be the case based on the code snippet provided), an attacker may attempt to inject malicious content in the header to perform a log injection attack. Using unverified or uncleaned user input during logging may lead to security issues such as sensitive information disclosure and tampering of log files. This situation is one of the common forms of log injection vulnerability. Therefore, you should not output unprocessed user input directly into the log file.
The text was updated successfully, but these errors were encountered:
In line 28 of the middleware/jwt_refresh_token_middleware.go file, the program uses fmt.Println(parts) to print the split header (the value obtained from the Authorization header). This is a potential security risk because if the value is controlled by the user (which appears to be the case based on the code snippet provided), an attacker may attempt to inject malicious content in the header to perform a log injection attack. Using unverified or uncleaned user input during logging may lead to security issues such as sensitive information disclosure and tampering of log files. This situation is one of the common forms of log injection vulnerability. Therefore, you should not output unprocessed user input directly into the log file.
The text was updated successfully, but these errors were encountered: