Tavis Ormandy of the Gentoo Linux Security Audit Team discovered two vulnerabilities in the GNU debugger. The first allows an attacker to execute arbitrary code with the privileges of the user running gdb if they can trick the user into loading a specially crafted executable (CVE-2005-1704).

He also discovered that gdb loads and executes the file .gdbinit in the current directory even if the file belongs to a different user. If a user can be tricked into running gdb in a directory with a malicious .gdbinit file, a local attacker can exploit this to run arbitrary commands with the privileges of the user running gdb (CVE-2005-1705).

The updated packages have been patched to correct these problems.

An updated gdb package that fixes several bugs and minor security issues is now available.

This update has been rated as having low security impact by the Red Hat Security Response Team.

GDB, the GNU debugger, allows debugging of programs written in C, C++, and other languages by executing them in a controlled fashion, then printing their data.

Several integer overflow bugs were found in gdb. If a user is tricked into processing a specially crafted executable file, it may allow the execution of arbitrary code as the user running gdb. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-1704 to this issue.

A bug was found in the way gdb loads .gdbinit files. When a user executes gdb, the local directory is searched for a .gdbinit file which is then loaded. It is possible for a local user to execute arbitrary commands as the victim running gdb by placing a malicious .gdbinit file in a location where gdb may be run. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-1705 to this issue.

This updated package also addresses the following issues :

  - GDB on ia64 had previously implemented a bug fix to     work-around a kernel problem when creating a core file     via gcore. The bug fix caused a significant slow-down of     gcore.

  - GDB on ia64 issued an extraneous warning when gcore was     used.

  - GDB on ia64 could not backtrace over a sigaltstack.

  - GDB on ia64 could not successfully do an info frame for     a signal trampoline.

  - GDB on AMD64 and Intel EM64T had problems attaching to a     32-bit process.

  - GDB on AMD64 and Intel EM64T was not properly handling     threaded watchpoints.

  - GDB could not build with gcc4 when -Werror flag was set.

  - GDB had problems printing inherited members of C++     classes.

  - A few updates from mainline sources concerning Dwarf2     partial die in cache support, follow-fork support,     interrupted syscall support, and DW_OP_piece read     support.

All users of gdb should upgrade to this updated package, which resolves these issues.

An update of the crash package has been released.

Tavis Ormandy found an integer overflow in the GNU debugger. By tricking an user into merely load a specially crafted executable, an attacker could exploit this to execute arbitrary code with the privileges of the user running gdb. However, loading untrusted binaries without actually executing them is rather uncommon, so the risk of this flaw is low. (CAN-2005-1704)

Tavis Ormandy also discovered that gdb loads and executes the file '.gdbinit' in the current directory even if the file belongs to a different user. By tricking an user into run gdb in a directory with a malicious .gdbinit file, a local attacker could exploit this to run arbitrary commands with the privileges of the user invoking gdb.
(CAN-2005-1705).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

いくつかのバグや重要度の低いセキュリティ問題を修正する、更新済みの gdb パッケージが、現在利用可能です。

この更新は、Red Hat セキュリティレスポンスチームによりセキュリティインパクトが小さいと評価されています。

GNU のデバッガーである GDB により、 C、C++、その他の言語をコントロールされている形で実行し、それらのデータを印刷することにより、それらの言語で書かれたプログラムのデバッグが可能です。

gdb にいくつかの整数オーバーフローの欠陥が見つかりました。ユーザーが騙されて特別に細工された実行可能ファイルを処理すると、gdb を実行しているユーザーとして任意のコードが実行される可能性があります。Common Vulnerabilities and Exposures プロジェクト（cve.mitre.org）は、この問題に CVE-2005-1704 の識別名を割り当てています。

gdb が .gdbinit ファイルをロードする方法で、バグが見つかりました。ユーザーが gdb を実行すると、.gdbinit ファイルのローカルディレクトリが検索され、これがロードされます。ローカルユーザーが、gdb を実行する可能性がある場所に悪意のある .gdbinit ファイルを配置することで、gdb を実行している被害者として、任意のコマンドを実行する可能性があります。Common Vulnerabilities and Exposures プロジェクト（cve.mitre.org）は、この問題に CVE-2005-1705 の識別名を割り当てています。

この更新パッケージは、次の問題にも対処しています。

- ia64 の GDB は、gcore でコアファイルを作成する場合のカーネルの問題に対処するバグ修正を実装していました。このバグ修正が、gcore の大幅な低減を引き起こしていました。

- ia64 の GDB は、gcore が使用されると、大量の警告を発しました。

- ia64 の GDB が、シグナルトラックをバックトレースしない可能性があります。

- ia64 の GDB が、シグナルトランポリンの情報フレームを正常に実行できない可能性があります。

- AMD64 および Intel EM64T の GDB に、32 ビットのプロセスへのアタッチの問題があります。

- AMD64 および Intel EM64T の GDB が、スレッド化したウォッチポイントを適切に処理していませんでした。

- -Werror フラグが設定されている場合、GDB は、gcc4 でビルドできない可能性があります。

- GDB に、C++ クラスの継承されたメンバーの印刷の問題があります。

- Dwarf2 に関するメインラインのソースからの若干の更新が、部分的に機能しないことがあり、それは、キャッシュのサポート、follow-fork のサポート、割り込まれた syscall のサポート、DW_OP_piece 読み取りサポートなどです。

gdb の全ユーザーは、この更新済みパッケージにアップグレードし、これらの問題を解決する必要があります。

修复了多个缺陷和次要安全问题的更新后的 gdb 程序包现在可用。

Red Hat 安全响应团队将此更新评级为具有低安全影响。

GDB（GNU 调试程序）允许调试以 C、C++ 及其他语言编写的程序，方法是以可控的方式执行它们，然后打印其数据。

在 gdb 中发现多个整数溢出缺陷。如果用户受到诱骗处理特别构建的可执行文件，则可能允许以运行 gdb 的用户的身份执行任意代码。通用漏洞和暴露计划 (cve.mitre.org) 已为此问题分配名称 CVE-2005-1704。

在 gdb 加载 .gdbinit 文件的方式中发现一个缺陷。用户执行 gdb 时，本地目录将搜索随后加载的 .gdbinit 文件。通过将恶意 .gdbinit 文件置于可能运行 gdb 的位置，本地用户可以以运行 gdb 的受害者的身份执行任意命令。通用漏洞和暴露计划 (cve.mitre.org) 已为此问题分配名称 CVE-2005-1705。

此更新后的程序包还解决了以下问题：

- ia64 上的 GDB 有以前实现的缺陷补丁，用于解决通过 gcore 创建核心文件时的内核问题。该缺陷补丁会导致 gcore 显著变慢。

- ia64 上的 GDB 在使用 gcore 时发出无关的警告。

- ia64 上的 GDB 无法通过 sigaltstack 回溯。

- ia64 上的 GDB 无法对信号 trampoline 成功执行 info frame。

- AMD64 和 Intel EM64T 上的 GDB 连接到 32 位进程时出现问题。

- AMD64 和 Intel EM64T 上的 GDB 未正确处理线程的观察点。

- 设置 -Werror 标记后，GDB 无法通过 gcc4 构建。

- GDB 打印继承的 C++ 类成员时出现问题。

- 来自干线来源的一些更新涉及缓存支持、跟随 fork 支持、中断的 syscall 支持以及 DW_OP_piece 读取支持中的 Dwarf2 部分终止。

所有 gdb 用户应升级此更新后的程序包，其中解决了这些问题。

現已提供更新版 gdb 套件，可修正數個錯誤與輕微的安全性問題。

Red Hat 安全性回應團隊已將此更新評等為具有低安全性影響。

GDB (GNU 除錯程式) 允許對使用 C、C++ 和其他語言撰寫的程式進行除錯，方法是以受到控制的方式執行這些程式，然後列印其資料。

在 gdb 中發現數個整數溢位錯誤。如果使用者遭誘騙而處理特製的可執行檔，則可允許以執行 gdb 之使用者的身分執行任意程式碼。Common Vulnerabilities and Exposures 專案 (cve.mitre.org) 已將名稱 CVE-2005-1704 指派給此問題。

在 gdb 載入 .gdbinit 檔案的方式中發現一個錯誤。使用者執行 gdb 時，系統會在本機目錄中搜尋隨後載入的 .gdbinit 檔案。本機使用者可在 gdb 可能執行的位置放置惡意.gdbinit 檔案，從而以執行 gdb 之受害者的身分執行任意命令。Common Vulnerabilities and Exposures 專案 (cve.mitre.org) 已將名稱 CVE-2005-1705 指派給此問題。

此更新版套件也可解決下列問題：

- 為因應透過 gcore 建立核心檔案時發生的核心問題，ia64 上的 GDB 先前會實作一個錯誤修正。而該錯誤修正會造成 gcore 效能大幅降低。

- 使用 gcore 時，ia64 上的 GDB 會發出無關的警告。

- ia64 上的 GDB 不會透過 sigaltstack 反向追蹤。

- ia64 上的 GDB 無法成功針對訊號 trampoline 執行資訊框架。

- AMD64 和 Intel EM64T 上的 GDB 無法附加至 32 位元組處理程序。

- AMD64 和 Intel EM64T 上的 GDB 無法正確處理執行緒的監控點。

- 在已設定 -Werror 旗標的情況下，GDB 無法以 gcc4 構建。

- GDB 無法列印 C++ 類別的繼承成員。

- 數個有關 Dwarf2 部分的主線來源更新在快取支援、遵循分支支援、中斷系統呼叫支援和 DW_OP_piece 讀取支援中停止回應。

所有 gdb 使用者皆升級至此更新版套件，其可解決這些問題。

The remote host is affected by the vulnerability described in GLSA-200505-15 (gdb: Multiple vulnerabilities)

    Tavis Ormandy of the Gentoo Linux Security Audit Team discovered an     integer overflow in the BFD library, resulting in a heap overflow. A     review also showed that by default, gdb insecurely sources     initialisation files from the working directory.
  Impact :

    Successful exploitation would result in the execution of arbitrary code     on loading a specially crafted object file or the execution of     arbitrary commands.
  Workaround :

    There is no known workaround at this time.

An updated gdb package that fixes minor security issues is now available.

This update has been rated as having low security impact by the Red Hat Security Response Team.

GDB, the GNU debugger, allows debugging of programs written in C, C++, and other languages by executing them in a controlled fashion, then printing their data.

Several integer overflow bugs were found in gdb. If a user is tricked into processing a specially crafted executable file, it may allow the execution of arbitrary code as the user running gdb. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-1704 to this issue.

A bug was found in the way gdb loads .gdbinit files. When a user executes gdb, the local directory is searched for a .gdbinit file which is then loaded. It is possible for a local user to execute arbitrary commands as the user running gdb by placing a malicious .gdbinit file in a location where gdb may be run. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2005-1705 to this issue.

All users of gdb should upgrade to this updated package, which contains backported patches that resolve these issues.

The remote Redhat Enterprise Linux 4 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2005:709 advisory.

    GDB, the GNU debugger, allows debugging of programs written in C, C++,     and other languages by executing them in a controlled fashion, then     printing their data.

    Several integer overflow bugs were found in gdb. If a user is tricked     into processing a specially crafted executable file, it may allow the     execution of arbitrary code as the user running gdb. The Common     Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name     CAN-2005-1704 to this issue.

    A bug was found in the way gdb loads .gdbinit files. When a user executes     gdb, the local directory is searched for a .gdbinit file which is then     loaded. It is possible for a local user to execute arbitrary commands as     the victim running gdb by placing a malicious .gdbinit file in a location     where gdb may be run. The Common Vulnerabilities and Exposures project     (cve.mitre.org) has assigned the name CAN-2005-1705 to this issue.

    This updated package also addresses the following issues:

    - GDB on ia64 had previously implemented a bug fix to work-around a kernel     problem when creating a core file via gcore.  The bug fix caused a     significant slow-down of gcore.

    - GDB on ia64 issued an extraneous warning when gcore was used.

    - GDB on ia64 could not backtrace over a sigaltstack.

    - GDB on ia64 could not successfully do an info frame for a signal trampoline.

    - GDB on AMD64 and Intel EM64T had problems attaching to a 32-bit process.

    - GDB on AMD64 and Intel EM64T was not properly handling threaded watchpoints.

    - GDB could not build with gcc4 when -Werror flag was set.

    - GDB had problems printing inherited members of C++ classes.

    - A few updates from mainline sources concerning Dwarf2 partial die in     cache support, follow-fork support, interrupted syscall support, and     DW_OP_piece read support.

    All users of gdb should upgrade to this updated package, which resolves     these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
18404	Mandrake Linux Security Advisory : gdb (MDKSA-2005:095)	Nessus	Mandriva Local Security Checks	2005/5/31	2021/1/6	high
67033	CentOS 4 : gdb (CESA-2005:709)	Nessus	CentOS Local Security Checks	2013/6/29	2021/1/4	high
203529	Photon OS 4.0: Crash PHSA-2023-4.0-0414	Nessus	PhotonOS Local Security Checks	2024/7/23	2024/7/23	critical
20526	Ubuntu 4.10 / 5.04 : gdb vulnerabilities (USN-135-1)	Nessus	Ubuntu Local Security Checks	2006/1/15	2021/1/19	high
67033	CentOS 4：gdb（CESA-2005:709）	Nessus	CentOS Local Security Checks	2013/6/29	2021/1/4	high
67033	CentOS 4：gdb (CESA-2005:709)	Nessus	CentOS Local Security Checks	2013/6/29	2021/1/4	high
67033	CentOS 4：gdb (CESA-2005:709)	Nessus	CentOS Local Security Checks	2013/6/29	2021/1/4	high
18379	GLSA-200505-15 : gdb: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	2005/5/28	2021/1/6	high
20059	RHEL 2.1 : gdb (RHSA-2005:801)	Nessus	Red Hat Local Security Checks	2005/10/19	2021/1/14	high
203822	Photon OS 3.0: Crash PHSA-2023-3.0-0601	Nessus	PhotonOS Local Security Checks	2024/7/24	2024/7/24	critical
19994	RHEL 4 : gdb (RHSA-2005:709)	Nessus	Red Hat Local Security Checks	2005/10/11	2024/11/4	high

检测

插件搜索

high

high

critical

high

high

high

high

high

high

critical

high