Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

CBase58Data::SetString: cleanse the full vector #7922

Merged
merged 1 commit into from Apr 22, 2016

Conversation

Projects
None yet
5 participants
Contributor

kazcw commented Apr 22, 2016

SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.
Contributor

paveljanik commented Apr 22, 2016

ACK 5770449

Owner

laanwj commented Apr 22, 2016

This one is sneaky, good catch.
utACK 5770449

Member

jonasschnelli commented Apr 22, 2016

Wow. Good catch!
utACK 5770449

@laanwj laanwj merged commit 5770449 into bitcoin:master Apr 22, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

laanwj added a commit that referenced this pull request Apr 22, 2016

Merge #7922: CBase58Data::SetString: cleanse the full vector
5770449 CBase58Data::SetString: cleanse the full vector (Kaz Wesley)

@kazcw kazcw deleted the kazcw:cleanse-fully branch Apr 29, 2016

MarcoFalke added a commit to MarcoFalke/bitcoin that referenced this pull request Jun 4, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449
Member

MarcoFalke commented Jun 9, 2016

Backported as part of #7938. Removing label 'Needs backport'.

zander added a commit to zander/bitcoinclassic that referenced this pull request Jun 16, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449

thokon00 added a commit to faircoin/faircoin that referenced this pull request Jun 28, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449

nomnombtc added a commit to nomnombtc/bitcoin that referenced this pull request Nov 12, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449

nomnombtc added a commit to nomnombtc/bitcoin that referenced this pull request Nov 12, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449

nomnombtc added a commit to nomnombtc/bitcoin that referenced this pull request Nov 13, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449

sickpig added a commit to sickpig/BitcoinUnlimited that referenced this pull request Nov 14, 2016

CBase58Data::SetString: cleanse the full vector
SetString seems to be passing the length of the wrong variable to
memory_cleanse, resulting in the last byte of the temporary buffer not being
securely erased.

Github-Pull: #7922
Rebased-From: 5770449

@dgenr8 dgenr8 referenced this pull request in bitcoinxt/bitcoinxt Jan 8, 2017

Merged

Cherries #184

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment