Frigate: Viewer-Role User Can Access go2rtc Internal API to obtain sensitive information
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| blakeblackshear | frigate | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Blakeblackshear | Frigate |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.366% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Blakeblackshear
Blakeblackshear frigate |
|
| Vendors & Products |
Blakeblackshear
Blakeblackshear frigate |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Frigate is an open source network video recorder. Prior to 0.18.0, the prefix-matched location /api/go2rtc/api in docker/main/rootfs/usr/local/nginx/conf/nginx.conf requires authentication but does not require an administrator role for GET requests, exposing the proxied go2rtc API to viewer users. An authenticated viewer can request the streams, config, log, and stack subpaths to obtain internal addresses, configuration paths, application logs, goroutine stack data, and RTSP stream URLs that may contain camera credentials. Non-GET methods remain blocked by limit_except GET. This issue is fixed in version 0.18.0. | |
| Title | Frigate: Viewer-Role User Can Access go2rtc Internal API to obtain sensitive information | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|