Summary
A critical improper authentication flaw in the Sofia IPC daemon allows WS-Security UsernameToken checks to accept the admin username with an arbitrary password when the account has an empty stored password. A remote attacker may then perform privileged ONVIF actions, including controlling PTZ functions, retrieving stream URLs, or rebooting the device, by sending a crafted SOAP request.
Affected context
The vulnerability occurs in Xiongmai IP Camera XM530 firmware HMT.CM2005-v220608.1837 and earlier when the Sofia IPC daemon exposes ONVIF services using WS-Security UsernameToken authentication. Risk is greatest when the ONVIF interface is reachable by an attacker and the administrative account has an empty stored password, allowing authentication logic to treat password verification as successful despite an arbitrary supplied password.
Exploit preconditions
- Attack surface: Network-accessible ONVIF SOAP service
- Required access: Network connectivity to the camera's ONVIF interface; valid administrator username knowledge may be sufficient
- Trigger point: WS-Security UsernameToken verification for an ONVIF request
- Account condition: The targeted administrative account must have an empty stored password
- Why exploitation is possible: The verification routine fails to properly reject arbitrary password values when the stored credential is empty, allowing privileged requests to pass authentication
Why this happens
The underlying bug is an authentication decision that does not require a valid password for a particular account state. Instead of treating an empty stored password as an invalid or explicitly configured credential condition, the WS-Security verification routine can accept a supplied username with an arbitrary password.
This behavior maps to CWE-287: Improper Authentication, because the system does not adequately verify that the requester possesses the required secret before authorizing privileged ONVIF operations.
Potential impact
- An attacker may bypass administrative authentication
- An attacker could control pan-tilt-zoom functions
- An attacker may retrieve camera stream URLs
- An attacker could reboot or disrupt camera availability
- Exposure of video feeds or device information may occur
- Compromised cameras could support broader network reconnaissance or intrusion
General mitigation guidance
Mitigation generally focuses on ensuring that every privileged authentication path requires a valid, non-empty credential and rejects ambiguous account states.
Common defensive patterns include:
- Enforcing strong, unique administrative passwords during provisioning
- Treating empty or missing stored passwords as authentication failures
- Using centralized, well-tested credential verification routines
- Applying explicit authorization checks to each privileged ONVIF action
- Restricting ONVIF exposure to trusted management networks or protected gateways
- Disabling unused remote administration and service interfaces
- Running camera services with only the permissions required for their functions
- Monitoring and limiting administrative SOAP requests at network boundaries
How teams detect issues like this
Organizations can identify similar weaknesses through:
- Static analysis for authentication branches that accept empty, null, or missing credentials
- Code review of WS-Security parsing, password comparison, and fallback logic
- Tests covering empty-password accounts, arbitrary-password submissions, and malformed authentication tokens
- Dynamic testing of every privileged ONVIF action with invalid credentials
- Network monitoring for unusual SOAP requests followed by PTZ changes, stream URL access, or reboots
- Policy enforcement requiring non-empty credentials and restricting ONVIF services to approved networks
Automated security testing and code review tools may help detect inconsistent authentication decisions, but privileged-action authorization should also be validated through targeted integration tests.

