From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Siddhesh Poyarekar <sipoyare@redhat.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 5/5] gdb: improve SECURITY.txt relating to embedded language bugs
Date: Mon, 12 Oct 2026 14:49:14 +0100 [thread overview]
Message-ID: <03796575f2fe79eb6f595a8a4fcd1548be12ea85.1791812758.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1791812758.git.aburgess@redhat.com>
The SECURITY.txt document has some text about how GDB provides access
to Python, Guile, and Shell interpreters, and how security bugs are
only a GDB security bug if the bug is specifically caused by GDB's
implementation, rather than being a consequence of having access to
these languages.
However, the existing language was maybe not as clear as it could be.
Currently we say:
"...and the effect can only be reproduced when executed in the GDB
environment."
I think it is clearer if we instead say:
"...and the effect is caused by a bug in GDB's implementation rather
than being an inherent consequence of the executed code, or being a
bug in the underlying language."
This tries to split the problem space into 3 cases:
(1) A bug in the underlying language is not a GDB bug.
(2) That GDB allows you to run harmful code via the extension
languages is not a GDB bug.
(3) A bug that only exists because of a bug in GDB's implementation
of the extension languages is a GDB bug.
---
gdb/SECURITY.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gdb/SECURITY.txt b/gdb/SECURITY.txt
index b484a1f65a1..f4bcc656406 100644
--- a/gdb/SECURITY.txt
+++ b/gdb/SECURITY.txt
@@ -122,9 +122,10 @@ What Is Not A Security Bug
GDB provides 3 different turing complete languages, Guile, Python
and direct access to the shell. Making use of these languages can
have unknown effects, including outside of the GDB process. Such
- effects will only be considered security bugs if they fit some of the
- definitions in this document and the effect can only be reproduced
- when executed in the GDB environment.
+ effects will only be considered security bugs if they fit some of
+ the definitions in this document and the effect is caused by a bug
+ in GDB's implementation rather than being an inherent consequence of
+ the executed code, or being a bug in the underlying language.
Any issues that arise from running an untrusted program outside of a
secure environment are not security bugs in GDB. Any issues that
--
2.25.4
next prev parent reply other threads:[~2026-10-12 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:49 [PATCH 0/5] SECURITY.txt changes Andrew Burgess
2026-10-12 13:49 ` [PATCH 1/5] gdb: fix minor grammar error in SECURITY.txt Andrew Burgess
2026-10-14 15:02 ` Tom Tromey
2026-10-12 13:49 ` [PATCH 2/5] gdb: extend SECURITY.txt to highlight additional remote debugging risks Andrew Burgess
2026-10-13 15:22 ` Siddhesh Poyarekar
2026-10-14 15:08 ` Tom Tromey
2026-10-14 16:10 ` Siddhesh Poyarekar
2026-10-16 14:24 ` Andrew Burgess
2026-10-16 14:27 ` Siddhesh Poyarekar
2026-10-12 13:49 ` [PATCH 3/5] gdb: extend SECURITY.txt discussion of DWARF/BFD parser bugs Andrew Burgess
2026-10-13 15:30 ` Siddhesh Poyarekar
2026-10-14 15:12 ` Tom Tromey
2026-10-14 16:16 ` Siddhesh Poyarekar
2026-10-14 17:28 ` Carlos O'Donell
2026-10-12 13:49 ` [PATCH 4/5] gdb: in SECURITY.txt, add notes on reporting exec and debug bugs Andrew Burgess
2026-10-12 13:49 ` Andrew Burgess [this message]
2026-10-14 15:44 ` [PATCH 0/5] SECURITY.txt changes Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03796575f2fe79eb6f595a8a4fcd1548be12ea85.1791812758.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sipoyare@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox