Show filters
75 Total Results
Displaying 11-20 of 75
Sort by:
Attacker Value
Unknown
CVE-2021-37967
Disclosure Date: October 08, 2021 (last updated February 23, 2025)
Inappropriate implementation in Background Fetch API in Google Chrome prior to 94.0.4606.54 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page.
0
Attacker Value
Unknown
CVE-2021-30630
Disclosure Date: October 08, 2021 (last updated February 23, 2025)
Inappropriate implementation in Blink in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page.
0
Attacker Value
Unknown
CVE-2021-41088
Disclosure Date: September 23, 2021 (last updated February 23, 2025)
Elvish is a programming language and interactive shell, combined into one package. In versions prior to 0.14.0 Elvish's web UI backend (started by `elvish -web`) hosts an endpoint that allows executing the code sent from the web UI. The backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost. All Elvish releases from 0.14.0 onward no longer include the the web UI, although it is still possible for the user to build a version from source that includes the web UI. The issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).
0
Attacker Value
Unknown
CVE-2020-27969
Disclosure Date: September 13, 2021 (last updated February 23, 2025)
Yandex Browser for Android 20.8.4 allows remote attackers to perform SOP bypass and addresss bar spoofing
0
Attacker Value
Unknown
CVE-2021-39185
Disclosure Date: September 01, 2021 (last updated February 23, 2025)
Http4s is a minimal, idiomatic Scala interface for HTTP services. In http4s versions 0.21.26 and prior, 0.22.0 through 0.22.2, 0.23.0, 0.23.1, and 1.0.0-M1 through 1.0.0-M24, the default CORS configuration is vulnerable to an origin reflection attack. The middleware is also susceptible to a Null Origin Attack. The problem is fixed in 0.21.27, 0.22.3, 0.23.2, and 1.0.0-M25. The original `CORS` implementation and `CORSConfig` are deprecated. See the GitHub GHSA for more information, including code examples and workarounds.
0
Attacker Value
Unknown
CVE-2021-34435
Disclosure Date: September 01, 2021 (last updated February 23, 2025)
In Eclipse Theia 0.3.9 to 1.8.1, the "mini-browser" extension allows a user to preview HTML files in an iframe inside the IDE. But with the way it is made it is possible for a previewed HTML file to trigger an RCE. This exploit only happens if a user previews a malicious file..
0
Attacker Value
Unknown
CVE-2021-39175
Disclosure Date: August 30, 2021 (last updated February 23, 2025)
HedgeDoc is a platform to write and share markdown. In versions prior to 1.9.0, an unauthenticated attacker can inject arbitrary JavaScript into the speaker-notes of the slide-mode feature by embedding an iframe hosting the malicious code into the slides or by embedding the HedgeDoc instance into another page. The problem is patched in version 1.9.0. There are no known workarounds aside from upgrading.
0
Attacker Value
Unknown
CVE-2021-30596
Disclosure Date: August 26, 2021 (last updated February 23, 2025)
Incorrect security UI in Navigation in Google Chrome on Android prior to 92.0.4515.131 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
0
Attacker Value
Unknown
CVE-2021-39270
Disclosure Date: August 18, 2021 (last updated February 23, 2025)
In Ping Identity RSA SecurID Integration Kit before 3.2, user impersonation can occur.
0
Attacker Value
Unknown
CVE-2021-37705
Disclosure Date: August 13, 2021 (last updated February 23, 2025)
OneFuzz is an open source self-hosted Fuzzing-As-A-Service platform. Starting with OneFuzz 2.12.0 or greater, an incomplete authorization check allows an authenticated user from any Azure Active Directory tenant to make authorized API calls to a vulnerable OneFuzz instance. To be vulnerable, a OneFuzz deployment must be both version 2.12.0 or greater and deployed with the non-default --multi_tenant_domain option. This can result in read/write access to private data such as software vulnerability and crash information, security testing tools and proprietary code and symbols. Via authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources. This issue is resolved starting in release 2.31.0, via the addition of application-level check of the bearer token's `issuer` against an administrator-configured allowlist. As a workaround users can restrict access to the tenant of a deployed OneFuzz instance < 2.31.0 by redeploying i…
0