Anjvision vulnerabilities
We track 6 vulnerabilities in Anjvision products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on September 29, 2026.
Latest Anjvision vulnerabilities
- 8.8 High severity
YSSD-RTMP-H5: Insufficiently Protected Credentials
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.
- 8.1 High severity
YSSD-RTMP-H5: Improper Check for Unusual or Exceptional Conditions
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
- 7.5 High severity
YSSD-RTMP-H5: Use of Hard-coded Credentials
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
- 8.8 High severity
YSSD-RTMP-H5: Improper Verification of Cryptographic Signature
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 introduc
- 8.8 High severity
YSSD-RTMP-H5: Improper Neutralization of Special Elements used in an OS Command
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 functi
- 9.8 Critical severity
YSSD-RTMP-H5: Initialization of a Resource with an Insecure Default
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.