GNS3 / GNS3/dynamips

Potential Null Pointer Dereference Vulnerability

Open
#309 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
405
Forks
99
Avg merge
3m
Merged PRs (30d)
1

Description

Hello,

I believe I may have found a possible null pointer dereference in the codebase.

The relevant function, file location, and the steps to trigger the issue are shown in the image below. Could you please help confirm whether this is a valid issue?

Thank you for your time.

Image

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 the attached image, which contains the reported function, file location, and trigger steps; inspect that referenced code path and reproduce the report. The work is done when the suspected null dereference is confirmed or ruled out and the result is recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.