<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src, branch v0.14.1.0</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.0</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.0'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2019-06-14T14:09:16Z</updated>
<entry>
<title>Merge pull request #5638</title>
<updated>2019-06-14T14:09:16Z</updated>
<author>
<name>Riccardo Spagni</name>
<email>ric@spagni.net</email>
</author>
<published>2019-06-14T14:09:16Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=29a505d1c1cfd3baa7d3a0c4433db8d7b043e341'/>
<id>urn:sha1:29a505d1c1cfd3baa7d3a0c4433db8d7b043e341</id>
<content type='text'>
6ed1679b prep for 0.14.1 release (Riccardo Spagni)
</content>
</entry>
<entry>
<title>rpc: restrict the recent cutoff size in restricted RPC mode</title>
<updated>2019-06-14T08:48:27Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-05-12T13:27:34Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=542cab02e1cc1acba09c4759826ef57bbd6c2191'/>
<id>urn:sha1:542cab02e1cc1acba09c4759826ef57bbd6c2191</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ensure no NULL is passed to memcpy</title>
<updated>2019-06-14T08:48:25Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-04-29T08:17:32Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=434e617a1d7f2f6f6b4507ada00f9ab69d0bd27e'/>
<id>urn:sha1:434e617a1d7f2f6f6b4507ada00f9ab69d0bd27e</id>
<content type='text'>
NULL is valid when size is 0, but memcpy uses nonnull attributes,
so let's not poke the bear
</content>
</entry>
<entry>
<title>serialization: check stream good flag at the end</title>
<updated>2019-06-14T08:48:19Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-04-16T18:48:40Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=756773e5fe79f970a36615cc178be09aedf4a915'/>
<id>urn:sha1:756773e5fe79f970a36615cc178be09aedf4a915</id>
<content type='text'>
just in case
</content>
</entry>
<entry>
<title>tree-hash: allocate variable memory on heap, not stack</title>
<updated>2019-06-14T08:48:16Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-04-04T00:15:07Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=e3f714aa2aee5f4a52671de30f48911edf042ea9'/>
<id>urn:sha1:e3f714aa2aee5f4a52671de30f48911edf042ea9</id>
<content type='text'>
Large amounts might run out of stack

Reported by guidov
</content>
</entry>
<entry>
<title>cryptonote: throw on tx hash calculation error</title>
<updated>2019-06-14T08:48:13Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-03-19T01:07:10Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=67baa3a66b07f5b6320911eed49ca91e2a5d037a'/>
<id>urn:sha1:67baa3a66b07f5b6320911eed49ca91e2a5d037a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>serialization: fail on read_varint error</title>
<updated>2019-06-14T08:48:10Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-03-11T23:36:17Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=d6bb9ecc6fe618840417df45f750dfb584cb549e'/>
<id>urn:sha1:d6bb9ecc6fe618840417df45f750dfb584cb549e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cryptonote_protocol: fix another potential P2P DoS</title>
<updated>2019-06-14T08:48:07Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-03-09T09:08:53Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=19490e44af187d5afe6fed7b23de468408c7896b'/>
<id>urn:sha1:19490e44af187d5afe6fed7b23de468408c7896b</id>
<content type='text'>
When asking for txes in a fluffy transaction, one might ask
for the same (large) tx many times
</content>
</entry>
<entry>
<title>cryptonote_protocol: expand basic DoS protection</title>
<updated>2019-06-14T08:48:04Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-03-08T19:17:20Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=fa4aa47ea06d935b41ef028eca9a246eb58bd162'/>
<id>urn:sha1:fa4aa47ea06d935b41ef028eca9a246eb58bd162</id>
<content type='text'>
Count transactions as well
</content>
</entry>
<entry>
<title>cryptonote_protocol_handler: prevent potential DoS</title>
<updated>2019-06-14T08:48:01Z</updated>
<author>
<name>anonimal</name>
<email>anonimal@getmonero.org</email>
</author>
<published>2019-03-09T09:11:44Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=3c953d53696d9ccdd195e6a2f02578a154266882'/>
<id>urn:sha1:3c953d53696d9ccdd195e6a2f02578a154266882</id>
<content type='text'>
Essentially, one can send such a large amount of IDs that core exhausts
all free memory. This issue can theoretically be exploited using very
large CN blockchains, such as Monero.

This is a partial fix. Thanks and credit given to CryptoNote author
'cryptozoidberg' for collaboration and the fix. Also thanks to
'moneromooo'. Referencing HackerOne report #506595.
</content>
</entry>
</feed>
