Security readout for executives and security teams
Plain-English summary
CVE-2018-25098 is a medium-severity denial-of-service issue in Blockmason credit-protocol, specifically the UCAC handler in CreditProtocol.sol. The project is unsupported and does not use versioning, so exposure depends on whether your organization still runs or relies on this code or a fork.
Executive priority
Treat this as a moderate priority unless the protocol is still used in production or supports financial workflows. Unsupported status increases operational risk because fixes, affected versions, and vendor support are limited.
Technical view
The CVE identifies CWE-404 in executeUcacTx within contracts/CreditProtocol.sol. Manipulation can cause denial of service with low availability impact. CVSS 3.1 is 4.3, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L. A patch commit is named, but affected and unaffected releases are unavailable.
Likely exposure
Exposure is likely limited to organizations using Blockmason credit-protocol, deployed derivatives, or forks containing the vulnerable UCAC handler. The product has no versioning, and sources state it is no longer supported, making inventory and code comparison necessary.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. The CVSS vector suggests adjacent access, low complexity, no privileges, and no user interaction, but the documented impact is limited to availability.
Researcher notes
Evidence is sparse: no versioning, unavailable affected-release boundaries, and no cited exploitation. Analysis should focus on code provenance, fork lineage, deployed contract equivalence, and whether the named patch is present.
Mitigation direction
- Inventory any use of Blockmason credit-protocol or forks.
- Compare local code with patch commit 082e01f18707ef995e80ebe97fcedb229a55efc5.
- Apply the referenced patch where the code remains in use.
- If unsupported code is business-critical, plan retirement or replacement.
- Check current vendor or community guidance before operational changes.
Validation and detection
- Search repositories for contracts/CreditProtocol.sol and executeUcacTx.
- Confirm whether deployed artifacts include the vulnerable UCAC handler logic.
- Review PR 33 and the patch commit against local code.
- Run availability-focused regression tests for patched UCAC transaction handling.
- Document any remaining unsupported deployments and compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-404: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-25098 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.252799CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.252799CVE reference · signature, permissions-required
- https://github.com/blockmason/credit-protocol/pull/33CVE reference · issue-tracking
- https://github.com/blockmason/credit-protocol/commit/082e01f18707ef995e80ebe97fcedb229a55efc5CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
