Bug 2209800 (CVE-2018-20587) - CVE-2018-20587 bitcoin: Incorrect Access Control
Summary: CVE-2018-20587 bitcoin: Incorrect Access Control
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2018-20587
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2209801 2209802
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-24 20:39 UTC by Patrick Del Bello
Modified: 2023-05-25 01:41 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 01:41:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Patrick Del Bello 2023-05-24 20:39:26 UTC
Source: bitcoin
X-Debbugs-CC: team.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for bitcoin.

CVE-2018-20587[0]:
| Bitcoin Core 0.12.0 through 0.17.1 and Bitcoin Knots 0.12.0 through
| 0.17.x before 0.17.1.knots20181229 have Incorrect Access Control.
| Local users can exploit this to steal currency by binding the RPC IPv4
| localhost port, and forwarding requests to the IPv6 localhost port.

https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2018-20587


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-20587
    https://www.cve.org/CVERecord?id=CVE-2018-20587

Please adjust the affected versions in the BTS as needed.

Comment 1 Patrick Del Bello 2023-05-24 20:40:29 UTC
Created bitcoin-core tracking bugs for this issue:

Affects: epel-all [bug 2209802]
Affects: fedora-all [bug 2209801]

Comment 2 Product Security DevOps Team 2023-05-25 01:41:39 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.