CVE-2025-45620

Issue details

Camera model PTC310UV2 running firmware version 0.1.0000.59. The vulnerability is found in the web interface that is used to access the camera. The vulnerability was found during a penetration test, thus, certain information in the PoC screenshots have been redacted.

Description

This disclosure contains two vulnerabilities that has been identified in the AVer firmware login web interface. It should be noted that I am not very familiar with any of your products, meaning that some terms might not be used correctly.

This finding is a bit more comprehensive compared to CVE-2025-45619, though, it mainly relates to client-side authentication. Inspecting the source code of the web application reveals the authentication mechanism that is being applied. When the authentication mechanism is performed on the frontend, it means that the application has to pull credentials from somewhere, in this case an endpoint, and into the frontend. In this case, the function displayed below pulls credentials from the endpoint identified in the first finding to the frontend.

The ‘SendAction(“Get=acc”, function(data)’ line makes a request to the first finding to pull the application which returns the credentials in a “username&password&” format. Next, the function parses the returned string and sets the username to “auth_user” and the password to “auth_pwd”. Finally, the function compares the values to those supplied by the user (name and pwd), and continues the login flow depending on whether the credentials are correct or not. The application makes the call for credentials whether the credentials are valid or not. This means that if an attacker monitors the network traffic in their browser, the username or password will be exposed – unencrypted. This process is displayed in the figures below.

Storing or transferring passwords in the frontend is in violation with best practice; instead, authentication should be handled securely using token-based methods (e.g., JWT, OAuth).