• Skip to primary navigation
  • Skip to main content
CVE Vulnerability

CVE Vulnerability

  • CVE’s
  • Products
  • Vendors

CWE-20

CVE-2018-1273

February 26, 2023 by

Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data’s projection-based request payload binding hat can lead to a remote code execution attack.

CVE-2018-1268

February 26, 2023 by

Cloud Foundry Loggregator, versions 89.x prior to 89.5 or 96.x prior to 96.1 or 99.x prior to 99.1 or 101.x prior to 101.9 or 102.x prior to 102.2, does not validate app GUID structure in requests. A remote authenticated malicious user knowing the GUID of an app may construct malicious requests to read from or write to the logs of that app.

CVE-2018-12688

February 26, 2023 by

tinyexr 0.9.5 has a segmentation fault in the wav2Decode function.

CVE-2018-12694

February 26, 2023 by

TP-Link TL-WA850RE Wi-Fi Range Extender with hardware version 5 allows remote attackers to cause a denial of service (reboot) via data/reboot.json.

CVE-2018-12702

February 26, 2023 by

The approveAndCallcode function of a smart contract implementation for Globalvillage ecosystem (GVE), an Ethereum ERC20 token, allows attackers to steal assets (e.g., transfer the contract’s balances into their account) because the callcode (i.e., _spender.call(_extraData)) is not verified, aka the “evilReflex” issue. NOTE: a PeckShield disclosure states “some researchers have independently discussed the mechanism of such vulnerability.”

CVE-2018-12703

February 26, 2023 by

The approveAndCallcode function of a smart contract implementation for Block 18 (18T), an tradable Ethereum ERC20 token, allows attackers to steal assets (e.g., transfer the contract’s balances into their account) because the callcode (i.e., _spender.call(_extraData)) is not verified, aka the “evilReflex” issue. NOTE: a PeckShield disclosure states “some researchers have independently discussed the mechanism of such vulnerability.”

  • « Go to Previous Page
  • Go to page 1
  • Interim pages omitted …
  • Go to page 244
  • Go to page 245
  • Go to page 246
  • Go to page 247
  • Go to page 248
  • Interim pages omitted …
  • Go to page 681
  • Go to Next Page »

Copyright CVE Vulnerabilities 2023
Data Sources:

  • NIST
  • MITRE
  • CVE Search
  • Open CVE