Fiber: HSTS header never set in helmet middleware due to incorrect protocol check
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gofiber | fiber | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gofiber | Fiber |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gv83-gqw6-9j2c | GoFiber never set HSTS header in helmet middleware due to incorrect protocol check |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.212% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gofiber
Gofiber fiber |
|
| Vendors & Products |
Gofiber
Gofiber fiber |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Fiber is an Express inspired web framework written in Go. Prior to 3.4.0, the helmet middleware in middleware/helmet/helmet.go never sets the Strict-Transport-Security response header even when HSTSMaxAge is configured because it checks c.Protocol() for https instead of c.Scheme(). This issue is fixed in version 3.4.0. | |
| Title | Fiber: HSTS header never set in helmet middleware due to incorrect protocol check | |
| Weaknesses | CWE-319 | |
| References |
| |
| Metrics |
cvssV3_1
|