MTC project MTC (M2C Mesh Network)
Approved changes feed: RSS · Atom
cpe:2.3:a:mtc_project:mtc:-:*:*:*:*:*:*:*part: a version: - update: *
| Vendor | Mtc Project (fff13044-60fe-582c-bd1e-a0a70afd845e) |
|---|---|
| Product | Mtc (8736b3b6-156e-5a84-aa08-d605077bfe9f) |
| 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-10769 |
vulnerable | 2026-06-08 05:10:37.083902 |
Details available
The transferProxy and approveProxy functions of a smart contract implementation for SmartMesh (SMT), an Ethereum ERC20 token, allow attackers to accomplish an unauthorized transfer of digital assets because replay attacks can occur with the same-named functions (with the same signatures) in other tokens: First (FST), GG Token (GG), M2C Mesh Network (MTC), M2C Mesh Network (mesh), and UG Token (UGT).
Published: 2018-08-10T15:00:00.000Z
Updated: 2024-08-05T07:46:46.626Z |
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.