OR
     *cpe:2.3:a:gofiber:fiber:*:*:*:*:*:*:*:* versions up to (excluding) 1.12.6

NIST (AV:N/AC:M/Au:N/C:P/I:P/A:N)

Victim must voluntarily interact with attack mechanism

NIST AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

NIST CWE-74

https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f No Types Assigned

https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f Patch, Third Party Advisory

https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh No Types Assigned

https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh Third Party Advisory

In Fiber before version 1.12.6, the filename that is given in c.Attachment() (https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc.

A possible workaround is to serialize the input before passing it to ctx.Attachment(

In Fiber before version 1.12.6, the filename that is given in c.Attachment() (https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc. A possible workaround is to serialize the input before passing it to ctx.Attachment()