New MCP server — Bring vulnerability intelligence into your AI
Back to feed

CVE-2025-57808

ExploitedNVDCIRCLENISA

EUVD-2025-26385 · Published Sep 2, 2025

ESP-IDF web_server basic auth bypass using empty or incomplete Authorization header

Summary

On the ESP-IDF platform, ESPHome's web_server authentication check can pass incorrectly when the client-supplied base64-encoded Authorization value is empty or is a substring of the correct value (e.g., correct username with partial password). This allows access to web_server functionality (including OTA, if enabled) without knowing any information about the correct username or password.

Details

The HTTP basic auth check in web_server_idf's AsyncWebServerRequest::authenticate only compares up to auth.value().size() - auth_prefix_len bytes of the base64-encoded user:pass string. This means a client-provided valuer like dXNlcjpz (user:s) will pass the check when the correct value is much longer, e.g., dXNlcjpzb21lcmVhbGx5bG9uZ3Bhc3M= (user:somereallylongpass).

Furthermore, the check will also pass when the supplied value is the empty string, which removes the need to know (or brute force) the username. A browser won't generally issue such a request, but it can easily be done by manually constructing the Authorizaztion request header (e.g., via curl).

PoC

Configure ESPHome as follows:

esp32:
  board: ...
  framework:
    type: esp-idf
web_server:
  auth:
    username: user
    password: somereallylongpass

In a browser, you can correctly log in by supplying username user and password somereallylongpass... but you can also incorrectly log in by supplying substrings of the password whose base64-encoded digest matches a prefix of the correct digest. (For example, I was able to log into an ESPHome device so configured by supplying password some... or even just s.)

You can also use a tool like curl to manually set an Authorization request header that always passes the check without any knowledge of the username:

$ curl -D- http://example.local/
HTTP/1.1 401 Unauthorized
...

$ curl -D- -H 'Authorization: Basic ' http://example.local/
HTTP/1.1 200 OK
...
Impact

This vulnerability effectively nullifies basic auth support for the ESP-IDF web_server, allowing auth bypass from another device on the local network with no knowledge of the correct username or password required.

Remediation

This vulnerability is fixed in 2025.8.1 and later.

For older versions, disabling the web_server component on ESP-IDF devices may be prudent, particularly if OTA updates through web_server are enabled.

Technologies

Esphome Esphome FirmwareEsphome Esphome

Weaknesses

CWE-303CWE-187

CVSS scores

  • v3.18.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

References

Potentially impacted assets

See if this affects your attack surface

Latest trending attack

Criticaltoday

MaxKB - Prompt Injection & OS Command Injection & Execution with Unnecessary Privileges

MaxKB is an open-source platform for building knowledge-base question-answering and AI agent applications. Its assistants can use tools, MCP tools, skills and sub-applications. CVE-2026-77521 Before version 2.10.5-lts, MaxKB assistants that use a tool, MCP tool, skill or sub-application rely on SandboxShellBackend. This exposes a shell execute tool that is not excluded and is left out of interrupt_on, so no human approval is required. Untrusted chat or ingested content can therefore make the agent run commands (prompt injection leading to command execution). Source deployments with MAXKB_SANDBOX disabled run the commands directly as the application user. In the official root container, a string-based gosu wrapper let shell metacharacters run outside the intended sandbox. The weaknesses are CWE-78, CWE-250 and CWE-749. CISA ADP SSVC rates exploitation as "poc", automatable as "yes" and technical impact as "total". Versions before 2.10.5-lts are affected, and 2.10.5-lts fixes the issue.

Take 15 minutes to discover our platform with our experts

Patrowl Intel platform screenshot