Show filters
323 Total Results
Displaying 141-150 of 323
Sort by:
Attacker Value
Unknown

CVE-2018-14679

Disclosure Date: July 28, 2018 (last updated November 27, 2024)
An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha. There is an off-by-one error in the CHM PMGI/PMGL chunk number validity checks, which could lead to denial of service (uninitialized data dereference and application crash).
0
Attacker Value
Unknown

CVE-2018-14682

Disclosure Date: July 28, 2018 (last updated November 27, 2024)
An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha. There is an off-by-one error in the TOLOWER() macro for CHM decompression.
0
Attacker Value
Unknown

CVE-2018-14680

Disclosure Date: July 28, 2018 (last updated November 27, 2024)
An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha. It does not reject blank CHM filenames.
0
Attacker Value
Unknown

CVE-2018-14681

Disclosure Date: July 28, 2018 (last updated November 27, 2024)
An issue was discovered in kwajd_read_headers in mspack/kwajd.c in libmspack before 0.7alpha. Bad KWAJ file header extensions could cause a one or two byte overwrite.
0
Attacker Value
Unknown

CVE-2018-14063

Disclosure Date: July 15, 2018 (last updated November 27, 2024)
The increaseApproval function of a smart contract implementation for Tracto (TRCT), an Ethereum ERC20 token, has an integer overflow.
0
Attacker Value
Unknown

CVE-2018-13469

Disclosure Date: July 09, 2018 (last updated November 27, 2024)
The mintToken function of a smart contract implementation for IcoContract, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
0
Attacker Value
Unknown

CVE-2018-13771

Disclosure Date: July 09, 2018 (last updated November 27, 2024)
The mintToken function of a smart contract implementation for ExacoreContract, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
0
Attacker Value
Unknown

TrackR Bravo MAC address can be exposed in close proximity and used to obtain t…

Disclosure Date: July 06, 2018 (last updated November 27, 2024)
The Trackr device ID is constructed of a manufacturer identifier of four zeroes followed by the BLE MAC address in reverse. The MAC address can be obtained by being in close proximity to the Bluetooth device, effectively exposing the device ID. The ID can be used to track devices. Updated apps, version 5.1.6 for iOS and 2.2.5 for Android, have been released by the vendor to address the vulnerabilities in CVE-2016-6538, CVE-2016-6539, CVE-2016-6540 and CVE-2016-6541.
0
Attacker Value
Unknown

TrackR Bravo is missing authentication for the cloud service and allows queryin…

Disclosure Date: July 06, 2018 (last updated November 27, 2024)
Unauthenticated access to the cloud-based service maintained by TrackR Bravo is allowed for querying or sending GPS data for any Trackr device by using the tracker ID number which can be discovered as described in CVE-2016-6539. Updated apps, version 5.1.6 for iOS and 2.2.5 for Android, have been released by the vendor to address the vulnerabilities in CVE-2016-6538, CVE-2016-6539, CVE-2016-6540 and CVE-2016-6541.
0
Attacker Value
Unknown

TrackR Bravo device allows unauthenticated pairing, which enables unauthenticat…

Disclosure Date: July 06, 2018 (last updated November 27, 2024)
TrackR Bravo device allows unauthenticated pairing, which enables unauthenticated connected applications to write to various device attributes. Updated apps, version 5.1.6 for iOS and 2.2.5 for Android, have been released by the vendor to address the vulnerabilities in CVE-2016-6538, CVE-2016-6539, CVE-2016-6540 and CVE-2016-6541.
0