PT-2023-7472 · Unknown · Google-Translate-Api-Browser
Pinkdraconian
·
Published
2023-11-24
·
Updated
2023-12-01
·
CVE-2023-48711
CVSS v3.1
3.7
Low
| Vector | AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N |
Name of the Vulnerable Software and Affected Versions
google-translate-api-browser versions prior to 4.1.3
Description
A Server-Side Request Forgery (SSRF) issue is present in applications utilizing the
google-translate-api-browser package and exposing the translateOptions to the end user. An attacker can set a malicious tld, causing the application to return unsafe URLs pointing towards local resources. The translateOptions.tld field is not properly sanitized before being placed in the Google translate URL. This can allow an attacker with control over the translateOptions to set the tld to a payload such as @127.0.0.1. This causes the full URL to become https://translate.google.@127.0.0.1/..., where translate.google. is the username used to connect to localhost. An attacker can send requests within internal networks and the local host. Should any HTTPS application be present on the internal network with a vulnerability exploitable via a GET call, then it would be possible to exploit this using this vulnerability.Recommendations
To resolve the issue, upgrade to release version 4.1.3 or later. As a temporary workaround, consider restricting access to the
translateOptions to prevent malicious tld settings. Additionally, restrict access to the vulnerable google-translate-api-browser package to minimize the risk of exploitation. Avoid using the tld parameter in the affected API endpoint until the issue is resolved.Exploit
Fix
SSRF
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Google-Translate-Api-Browser