DBL GoIP-1 up to GHSFVT-1.1-67-5 frame.html path filename control

Summaryinfo

A vulnerability, which was classified as problematic, was found in DBL GoIP-1 up to GHSFVT-1.1-67-5. The impacted element is an unknown function of the file frame.html. Such manipulation of the argument path leads to filename control. This vulnerability is documented as CVE-2022-4982. The attack needs to be performed locally. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in DBL GoIP-1 up to GHSFVT-1.1-67-5. It has been rated as problematic. Affected by this issue is some unknown functionality of the file frame.html. The manipulation of the argument path with an unknown input leads to a filename control vulnerability. Using CWE to declare the problem leads to CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. Impacted is confidentiality, integrity, and availability. CVE summarizes:

DBLTek GoIP-1 firmware versions up to and including GHSFVT-1.1-67-5 contain a local file inclusion vulnerability. The device's web server exposes handlers (`frame.html` and `frame.A100.html`) that accept a path parameter (`content` or `sidebar`) which is not properly validated or canonicalized. An attacker can supply directory-traversal sequences to cause the server to read and return arbitrary filesystem files that the webserver user can access. Other GoIP models and firmware versions are likely affected. Exploitation evidence was observed by the Shadowserver Foundation on 2024-03-21 UTC.

The weakness was released by Valtteri Lehtinen and Lassi Korhonen. The advisory is available at shufflingbytes.com. This vulnerability is handled as CVE-2022-4982 since 11/12/2025. The exploitation is known to be easy. Local access is required to approach this attack. Technical details as well as a public exploit are known.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:frame.html it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (50775). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• DBL

Name

• GoIP-1

Version

• GHSFVT-1.1-67-5

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion