8.2 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): Low (L)
- Integrity (I): High (H)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): Low (L)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): None (N)
Activity log
- Created suggestion
WLED Unauthenticated Configuration Disclosure via /json/cfg and Global Settings-PIN Lock State
WLED's GET /json/cfg endpoint (registered in wled00/wled_server.cpp) calls serveJson() with no settings-PIN check, unlike the /edit endpoint which explicitly checks correctPIN, disclosing the device's general configuration (network, hardware, LED setup) to any unauthenticated client on the network. Separately, the settings-PIN unlock state is tracked via a single global boolean `correctPIN` (wled00/wled.h), not per-session state: once any single client submits the correct 4-digit PIN via POST /json, correctPIN becomes true for every client, granting all subsequent unauthenticated clients full configuration-write access (OTA firmware updates, WiFi reconfiguration, factory reset) until the device reboots.
References
Affected products
- =<*
Matching in nixpkgs
pkgs.python313Packages.wled
Asynchronous Python client for WLED
pkgs.python314Packages.wled
Asynchronous Python client for WLED
pkgs.haskellPackages.wled-json
Convenient interface for interacting with WLED devices
pkgs.typstPackages.knowledge-key
None
pkgs.typstPackages.knowledge-key_1_0_0
None
pkgs.typstPackages.knowledge-key_1_0_1
None
pkgs.typstPackages.knowledge-key_1_0_2
None
pkgs.rubyPackages.cocoapods-acknowledgements
None
Package maintainers
-
@mweinelt Martin Weinelt <hexa@darmstadt.ccc.de>