Userwallet Project Userwallet
Approved changes feed: RSS · Atom
cpe:2.3:a:userwallet_project:userwallet:-:*:*:*:*:*:*:*part: a version: - update: *
| Vendor | Userwallet Project (e623dc73-5e75-59e1-a6e4-19d1cca0df61) |
|---|---|
| Product | Userwallet (3c1c5c31-8578-56f3-9bdc-c6bbce523b48) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-14085 |
vulnerable | 2026-06-08 05:10:52.692419 |
Details available
An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function sweep(address _token, uint _amount) returns (bool) { start = 0x123456789; return true;} }. Then, when one calls the function sweep() in the UserWallet contract, it will change the sweeperList to 0X123456789.
Published: 2018-07-16T02:00:00.000Z
Updated: 2024-09-16T16:22:39.933Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.