Skip to content

128tx exploit #1

Activity

  1. xmrig commented on Apr 21, 2017

    @xmrig
    Owner

    Ok the task looks easy, add variable length support for blob (76+). It's right?

    One moment unclear, what is the upper limit? 128 or more? in xmr-stak-cpu code I see 112. It's little bit confusing. Thank you.

  2. fireice-uk commented on Apr 21, 2017

    @fireice-uk

    The maximum length is 75 fixed + 9 variable so 84. I have a habit of rounding the sizeof manually sometimes.

  3. xmrig commented on Apr 22, 2017

    @xmrig
    Owner

    @fireice-uk

    piNonce = (uint32_t*)(oWork.bWorkBlob + 39);
    

    It's ok? looks like another magic number.

  4. fireice-uk commented on Apr 23, 2017

    @fireice-uk

    This is the nonce position in the miner's blob. The variable length fields that are included there are major_version, minor_version and timestamp. None of them are under control of the end user enough to make stuff fall out of place (section 4.1 here https://cryptonote.org/cns/cns003.txt )

    If you want to avoid magic numbers completely then you can parse the whole thing ( see section 1.2 here for a public domain parsing code https://tukaani.org/xz/xz-file-format.txt ).

  5. smoresmores commented on Aug 31, 2017

    @smoresmores

    Is this issue solved? @xmrig

  6. xmrig commented on Aug 31, 2017

    @xmrig
    Owner

    Probably yes, at least three no overflows now, but I not 100% sure it works as expected.

  7. added a commit that references this issue on Feb 17, 2018
  8. added a commit that references this issue on Dec 3, 2021
  9. added a commit that references this issue on Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions