Missing Authentication in Default Configuration in boneIO
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.6.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
boneIO Black firmware, the device software that runs its management web interface, ships with authentication turned off by default, so anyone on the network can control the device and the physical circuits it operates. An attacker could use this to disrupt the device, change its configuration, or switch connected equipment on and off.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
boneIO Black firmware ships with authentication disabled by default. Its management web API listens on all network interfaces and exposes all endpoints without requiring credentials. An unauthenticated remote attacker can fully control the device, causing denial of service, modifying configuration, and operating connected physical circuits. This issue was fixed in version 1.6.0: a device without an administrator account refuses API requests until the owner creates one in the first-run wizard, and every API route is restricted to an authenticated role. Versions before 1.2.0 are based on Debian 10, are no longer supported and cannot be upgraded in place; affected devices should be re-flashed with the 1.6.0 system image.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- boneio
From 1.0.0 · fixed in 1.6.0