Adding guards against possible NULL pointers dereference

Open
#98,998 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
security

Research direction

Review original_report.txt and Python3.11_static_analysis_result.txt, then reproduce the reported analysis with ./configure and infer run -- make --keep-going. The report names possible NULL-pointer dereferences but does not identify a bounded set of files or fixes. Done would require validating each finding and addressing confirmed vulnerabilities with appropriate tests.

Written by the indexing model from the issue text.

Description

type-bug

Bug report

Infer is a static analysis tool.
I used it to analyze CPython code base and got some interesting results.

I used the following command to complete the static analysis and got the original results in the attachment original_report.txt.
./configure
infer run -- make --keep-going

I've stripped out some of the more obvious false positives in the attachment Python3.11_static_analysis_result.txt,
the rest are vulnerabilities that I think may need attention.

Python is my favorite programming language. I hope this deicovery is helpful.

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

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.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.