m4b / m4b/goblin

Found a possible out of bound memory access in RelocationsData

Open
#469 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.5k
Forks
202
PR merge metrics
No merged PRs in 30d

Description

While fuzzing my project that depends on goblin, I found another out of bounds access. The PR with the sample and a fix can be found here: https://github.com/m4b/goblin/pull/468

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with RelocationsData and inspect the sample and proposed fix in pull request #468. Reproduce the reported out-of-bounds access using the linked sample, then verify that the issue no longer occurs and that the relevant tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
reverse-engineering
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.