Server-Side Request Forgery (SSRF) Affecting org.webjars.npm:google-translate-api-browser package, versions [0,]


Severity

Recommended
0.0
low
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of concept
EPSS
0.07% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JAVA-ORGWEBJARSNPM-6097155
  • published7 Dec 2023
  • disclosed24 Nov 2023
  • creditPinkDraconian

Introduced: 24 Nov 2023

CVE-2023-48711  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for org.webjars.npm:google-translate-api-browser.

Overview

org.webjars.npm:google-translate-api-browser is an A free and unlimited API for Google Translate that works in browser

Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) when input to translateOptions is accepted from the end user. An attacker can manipulate the tld field, causing the application to generate unsafe URLs that point to local resources. This is due to the translateOptions.tld field not being properly sanitized before being included in the Google translate URL. An attacker with control over the translateOptions can set the tld to a payload such as @127.0.0.1, which results in the full URL becoming https://translate.google.@127.0.0.1/..., where translate.google. is the username used to connect to localhost. This allows the attacker to send requests within internal networks and the local host. If there is an HTTPS application on the internal network with a vulnerability that can be exploited via a GET call, it could be exploited using this vulnerability.

References

CVSS Scores

version 3.1