]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.14] gh-148022: Add threat model to remote debugging docs (GH-148024) (#148039)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 3 Apr 2026 14:34:36 +0000 (16:34 +0200)
committerGitHub <noreply@github.com>
Fri, 3 Apr 2026 14:34:36 +0000 (14:34 +0000)
commit3d49e490e21efaa5ed251c26726f6a9052151a0e
tree1bfe0b9282950f6d177dfc705f3f7d6602ab3c74
parent6996c8303b13cfe20067f0adffb668565d5707ab
[3.14] gh-148022: Add threat model to remote debugging docs (GH-148024) (#148039)

gh-148022: Add threat model to remote debugging docs (GH-148024)

The remote debugging protocol has been generating spurious
vulnerability reports from automated scanners that pattern-match
on "remote access" and "memory operations" without understanding
the privilege model. This section documents the security boundaries
so reporters can self-triage before submitting.

The threat model clarifies three points: attaching requires the
same OS-level privileges as GDB (ptrace, task_for_pid, or
SeDebugPrivilege), crashes caused by reading corrupted target
process memory are not security issues, and a compromised target
process is out of scope. A subsection explains when operators
should use PYTHON_DISABLE_REMOTE_DEBUG for defence-in-depth.
(cherry picked from commit edab6860a7d6c49b5d5762e1c094aa0261245a9c)

Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
Doc/howto/remote_debugging.rst