CVE-2026-100295

In Anjvision YSSD‑RTMP‑H5 firmware version 3.3.2.4, the serial console includes a legacy password hash based on weak DES encryption.

In Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4, two user-information endpoints can reveal sensitive device and account details under conditions that are not intended for normal operation.

In Anjvision YSSD‑RTMP‑H5 firmware version 3.3.2.4, an unauthenticated network check function can be triggered to probe arbitrary hosts from the device's internal network, potentially exposing internal information or leaking data via DNS queries.

In Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4, an empty-body POST to /setUserConfig, dispatched through the web server's SOAP-RPC handler, silently downgrades the administrator password to the default value and corrupts the in-memory authentication state until the device reloads. The handler does not verify the session's privilege level, so any authenticated user can trigger it.

In Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4, the firmware embeds hardcoded cloud-API credentials that are shared across deployed devices. Anyone obtaining the public firmware package can reuse these values to interact with the cloud service in ways not intended for normal operation.

In Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4, both the local and cloud update mechanisms apply new firmware without any cryptographic verification, relying only on basic hashing. This design allows an attacker who can reach the update routine to introduce untrusted firmware images that the device will accept as valid.

In Anjvision YSSD-RTMP-H5 firmware version 3.3.2.4, a hidden debug interface can be enabled through an authenticated request, allowing additional commands to be sent to a backend service. Once active, this pathway can unintentionally expose system-level functionality that could be misused if crafted inputs reach the underlying command handler.

In Anjvision YSSD‑RTMP‑H5 firmware version 3.3.2.4, several ONVIF service endpoints process management requests without enforcing required authentication. This could allow an unauthorized attacker to access sensitive device operations.