LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20154: ghostlander Phoenixcoin main.cpp accept denial of service

A vulnerability was found in ghostlander Phoenixcoin. It has been classified as problematic. Affected is the function CTxMemPool::accept of the file src/main.cpp. The manipulation leads to denial of service. Upgrading to version 0.6.6.1-pxc is able to address this issue. The name of the patch is 987dd68f71a7d8276cef3b6c3d578fd4845b5699. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-217068.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Phoenixcoin software had a low-severity denial-of-service flaw in transaction memory pool handling. The cited impact is limited availability loss, with no confidentiality or integrity impact in the CVSS data. Organizations only need urgency if they run affected ghostlander Phoenixcoin components.

Executive priority

Treat as routine patch management unless Phoenixcoin availability is business-critical. The known impact is limited service disruption, but unpatched cryptocurrency infrastructure can still create operational risk if nodes support transactions, customer services, or monitoring.

Technical view

CVE-2017-20154 affects CTxMemPool::accept in src/main.cpp of ghostlander Phoenixcoin. Manipulation of this path can cause denial of service. Sources classify it as CWE-404 with CVSS 3.1 score 3.5: adjacent vector, low complexity, low privileges, no user interaction, and low availability impact.

Likely exposure

Exposure appears limited to environments running ghostlander Phoenixcoin before the fixed 0.6.6.1-pxc release. The source bundle does not provide a precise vulnerable version range or CPEs, so asset owners should verify deployed code or package versions directly.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, or exploit availability. The CVSS vector indicates exploitation requires adjacent access and low privileges, making broad internet-scale risk less likely from the supplied evidence.

Researcher notes

Evidence is narrow: VulDB and CVE data identify the affected function, denial-of-service impact, CWE-404, and fixed release, but not detailed vulnerable version ranges. Avoid assuming impact on other coin clients or forks without code comparison.

Mitigation direction

  • Upgrade Phoenixcoin to version 0.6.6.1-pxc or a later vendor-fixed release.
  • Verify the patch commit 987dd68f71a7d8276cef3b6c3d578fd4845b5699 is present.
  • Prioritize nodes providing business-critical wallet, exchange, or service availability.
  • If upgrade timing is unclear, check current vendor guidance before applying compensating controls.

Validation and detection

  • Inventory systems running ghostlander Phoenixcoin components.
  • Confirm installed version is 0.6.6.1-pxc or later.
  • Check source builds for patch commit 987dd68f71a7d8276cef3b6c3d578fd4845b5699.
  • Review monitoring for unexplained Phoenixcoin node crashes or availability degradation.
  • Document any exposed Phoenixcoin services and their network adjacency assumptions.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2017-20154 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
3.5CVSS 3.1LowCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2017-20154Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ghostlanderPhoenixcoinn/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-404 · source CWE mapping

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.