The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:0898-1 advisory.

  - The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library     (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows     remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have     unspecified other impact via a crafted ELF file. (CVE-2017-16829)

  - In the coff_pointerize_aux function in coffgen.c in the Binary File Descriptor (BFD) library (aka libbfd),     as distributed in GNU Binutils 2.30, an index is not validated, which allows remote attackers to cause a     denial of service (segmentation fault) or possibly have unspecified other impact via a crafted file, as     demonstrated by objcopy of a COFF object. (CVE-2018-7208)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

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

An update of the binutils package has been released.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2024:4413-1 advisory.

    Mention changes in GDB 14:

    * GDB now supports the AArch64 Scalable Matrix Extension 2       (SME2), which includes a new 512 bit lookup table register       named ZT0.
    * GDB now supports the AArch64 Scalable Matrix Extension (SME),       which includes a new matrix register named ZA, a new thread       register TPIDR2 and a new vector length register SVG       (streaming vector granule).  GDB also supports tracking ZA       state across signal frames.  Some features are still under       development or are dependent on ABI specs that are still in       alpha stage.  For example, manual function calls with ZA state       don't have any special handling, and tracking of SVG changes       based on DWARF information is still not implemented, but there       are plans to do so in the future.
    * GDB now recognizes the NO_COLOR environment variable and       disables styling according to the spec.  See       https://no-color.org/.  Styling can be re-enabled with       'set style enabled on'.
    * The AArch64 'org.gnu.gdb.aarch64.pauth' Pointer Authentication       feature string has been deprecated in favor of the       'org.gnu.gdb.aarch64.pauth_v2' feature string.
    * GDB now has some support for integer types larger than 64 bits.
    * Multi-target feature configuration.
      GDB now supports the individual configuration of remote       targets' feature sets.  Based on the current selection of a       target, the commands 'set remote <name>-packet (on|off|auto)'       and 'show remote <name>-packet' can be used to configure a       target's feature packet and to display its configuration,       respectively.
    * GDB has initial built-in support for the Debugger Adapter       Protocol.
    * For the break command, multiple uses of the 'thread' or 'task'       keywords will now give an error instead of just using the       thread or task id from the last instance of the keyword.  E.g.:
        break foo thread 1 thread 2       will now give an error rather than using 'thread 2'.
    * For the watch command, multiple uses of the 'task' keyword will       now give an error instead of just using the task id from the       last instance of the keyword.  E.g.:
        watch my_var task 1 task 2       will now give an error rather than using 'task 2'.  The       'thread' keyword already gave an error when used multiple times       with the watch command, this remains unchanged.
    * The 'set print elements' setting now helps when printing large       arrays.  If an array would otherwise exceed max-value-size, but       'print elements' is set such that the size of elements to print       is less than or equal to 'max-value-size', GDB will now still       print the array, however only 'max-value-size' worth of data       will be added into the value history.
    * For both the break and watch commands, it is now invalid to use       both the 'thread' and 'task' keywords within the same command.
      For example the following commnds will now give an error:
        break foo thread 1 task 1         watch var thread 2 task 3
    * The printf command now accepts a '%V' output format which will       format an expression just as the 'print' command would.  Print       options can be placed withing '[...]' after the '%V' to modify       how the value is printed.  E.g:
        printf '%V', some_array         printf '%V[-array-indexes on]', some_array       will print the array without, or with array indexes included,       just as the array would be printed by the 'print' command.
      This functionality is also available for dprintf when       dprintf-style is 'gdb'.
    * When the printf command requires a string to be fetched from       the   inferior, GDB now uses the existing 'max-value-size'       setting to the limit the memory allocated within GDB.  The       default 'max-value-size' is 64k.  To print longer strings you       should increase 'max-value-size'.
    * The Ada 2022 Enum_Rep and Enum_Val attributes are now       supported.
    * The Ada 2022 target name symbol ('@') is now supported by the       Ada expression parser.
    * The 'list' command now accepts '.' as an argument, which tells       GDB to print the location around the point of execution within       the current frame.  If the inferior hasn't started yet, the       command will print around the beginning of the 'main' function.
    * Using the 'list' command with no arguments in a situation where       the command would attempt to list past the end of the file now       warns the user that the end of file has been reached, refers       the user to the newly added '.' argument
    * Breakpoints can now be inferior-specific.  This is similar to       the   existing thread-specific breakpoint support.  Breakpoint       conditions can include the 'inferior' keyword followed by an       inferior id (as displayed in the 'info inferiors' output).
      It is invalid to use the 'inferior' keyword with either the       'thread' or 'task' keywords when creating a breakpoint.
    * New convenience function '$_shell', to execute a shell command       and return the result.  This lets you run shell commands in       expressions.  Some examples:
       (gdb) p $_shell('true')        $1 = 0        (gdb) p $_shell('false')        $2 = 1        (gdb) break func if $_shell('some command') == 0
    * New commands:

      * set debug breakpoint on|off         show debug breakpoint         Print additional debug messages about breakpoint insertion         and removal.
      * maintenance print record-instruction [ N ]         Print the recorded information for a given instruction.  If N         is not given prints how GDB would undo the last instruction         executed.  If N is negative, prints how GDB would undo the         N-th previous instruction, and if N is positive, it prints         how GDB will redo the N-th following instruction.
      * maintenance info frame-unwinders         List the frame unwinders currently in effect, starting with         the highest priority.
      * maintenance wait-for-index-cache         Wait until all pending writes to the index cache have         completed.
      * set always-read-ctf on|off         show always-read-ctf         When off, CTF is only read if DWARF is not present.  When on,         CTF is read regardless of whether DWARF is present.  Off by         default.
      * info main         Get main symbol to identify entry point into program.
      * set tui mouse-events [on|off]         show tui mouse-events         When on (default), mouse clicks control the TUI and can be         accessed by Python extensions.  When off, mouse clicks are         handled by the terminal, enabling terminal-native text         selection.

    * MI changes:

      * MI version 1 has been removed.
      * mi now reports 'no-history' as a stop reason when hitting the         end of the reverse execution history.
      * When creating a thread-specific breakpoint using the '-p'         option, the -break-insert command would report the 'thread'         field twice in the reply.  The content of both fields was         always identical.  This has now been fixed; the 'thread'         field will be reported just once for thread-specific         breakpoints, or not at all for breakpoints without a thread         restriction.  The same is also true for the 'task' field of         an Ada task-specific breakpoint.
        * It is no longer possible to create a thread-specific         breakpoint for a thread that doesn't exist using         '-break-insert -p ID'.  Creating breakpoints for         non-existent threads is not allowed when using the CLI, that         the MI allowed it was a long standing bug, which has now         been fixed.
      * The '--simple-values' argument to the         '-stack-list-arguments','-stack-list-locals',         '-stack-list-variables', and '-var-list-children' commands now         takes reference types into account: that is, a value is now         considered simple if it is neither an array, structure, or         union, nor a reference to an array, structure, or union.
        (Previously all references were considered simple.)  Support         for this feature can be verified by using the         '-list-features' command, which should contain         'simple-values-ref-types'.
      * The -break-insert command now accepts a '-g thread-group-id'         option to allow for the creation of inferior-specific         breakpoints.
      * The bkpt tuple, which appears in breakpoint-created         notifications, and in the result of the -break-insert         command can now include an optional 'inferior' field for both         the main breakpoint, and each location, when the breakpoint         is inferior-specific.

    * Python API:

      * gdb.ThreadExitedEvent added.  Emits a ThreadEvent.
      * The gdb.unwinder.Unwinder.name attribute is now read-only.
      * The name argument passed to gdb.unwinder.Unwinder.__init__         must now be of type 'str' otherwise a TypeError will be         raised.
      * The gdb.unwinder.Unwinder.enabled attribute can now only         accept values of type 'bool'.  Changing this attribute will         now invalidate GDB's frame-cache, which means GDB will need         to rebuild its frame-cache when next required - either with,         or without the particular unwinder, depending on how         'enabled' was changed.
      * New methods added to the gdb.PendingFrame class.  These         methods have the same behaviour as the corresponding         methods on gdb.Frame.  The new methods are:
        * gdb.PendingFrame.name: Return the name for the frame's           function, or None.
        * gdb.PendingFrame.is_valid: Return True if the pending           frame object is valid.
        * gdb.PendingFrame.pc: Return the $pc register value for           this frame.
        * gdb.PendingFrame.language: Return a string containing the           language for this frame, or None.
        * gdb.PendingFrame.find_sal: Return a gdb.Symtab_and_line           object for the current location within the pending frame,           or None.
        * gdb.PendingFrame.block: Return a gdb.Block for the current           pending frame, or None.
        * gdb.PendingFrame.function: Return a gdb.Symbol for the           current pending frame, or None.
      * The frame-id passed to gdb.PendingFrame.create_unwind_info         can now use either an integer or a gdb.Value object for each         of its 'sp', 'pc', and 'special' attributes.
      * A new class gdb.unwinder.FrameId has been added.  Instances         of this class are constructed with 'sp' (stack-pointer) and         'pc' (program-counter) values, and can be used as the         frame-id when calling gdb.PendingFrame.create_unwind_info.
      * It is now no longer possible to sub-class the         gdb.disassembler.DisassemblerResult type.
      * The Disassembler API from the gdb.disassembler module has         been extended to include styling support:
        * The DisassemblerResult class can now be initialized with a           list of parts.  Each part represents part of the           disassembled instruction along with the associated style           information.  This list of parts can be accessed with the           new DisassemblerResult.parts property.
        * New constants gdb.disassembler.STYLE_* representing all the           different styles part of an instruction might have.
        * New methods DisassembleInfo.text_part and           DisassembleInfo.address_part which are used to create the           new styled parts of a disassembled instruction.
        * Changes are backwards compatible, the older API can still           be used to disassemble instructions without styling.
      * New function gdb.execute_mi(COMMAND, [ARG]...), that invokes         a GDB/MI command and returns the output as a Python         dictionary.
      * New function gdb.block_signals().  This returns a context         manager that blocks any signals that GDB needs to handle         itself.
      * New class gdb.Thread.  This is a subclass of threading.Thread         that calls gdb.block_signals in its 'start' method.
      * gdb.parse_and_eval now has a new 'global_context' parameter.
        This can be used to request that the parse only examine         global symbols.
      * gdb.Inferior now has a new 'arguments' attribute.  This holds         the command-line arguments to the inferior, if known.
      * gdb.Inferior now has a new 'main_name' attribute.  This holds         the name of the inferior's 'main', if known.
      * gdb.Inferior now has new methods 'clear_env', 'set_env', and         'unset_env'.  These can be used to modify the inferior's         environment before it is started.
      * gdb.Value now has the 'assign' method.
      * gdb.Value now has the 'to_array' method.  This converts an         array-like Value to an array.
      * gdb.Progspace now has the new method 'objfile_for_address'.
        This returns the gdb.Objfile, if any, that covers a given         address.
      * gdb.Breakpoint now has an 'inferior' attribute.  If the         Breakpoint object is inferior specific then this attribute         holds the inferior-id (an integer).  If the Breakpoint         object is not inferior specific, then this field contains         None.  This field can be written too.
      * gdb.Type now has the 'is_array_like' and 'is_string_like'         methods.  These reflect GDB's internal idea of whether a         type might be array- or string-like, even if they do not         have the corresponding type code.
      * gdb.ValuePrinter is a new class that can be used as the base         class for the result of applying a pretty-printer.  As a         base class, it signals to gdb that the printer may implement         new pretty-printer methods.
      * New attribute Progspace.symbol_file.  This attribute holds         the gdb.Objfile that corresponds to Progspace.filename (when         Progspace.filename is not None), otherwise, this attribute is         itself None.
      * New attribute Progspace.executable_filename.  This attribute         holds a string containing a file name set by the 'exec-file'         or 'file' commands, or None if no executable file is set.
        This isn't the exact string passed by the user to these         commands; the file name will have been partially resolved to         an absolute file name.
      * A new executable_changed event registry is available.  This         event emits ExecutableChangedEvent objects, which have         'progspace' (a gdb.Progspace) and 'reload' (a Boolean)         attributes.  This event is emitted when         gdb.Progspace.executable_filename changes.
      * New event registries gdb.events.new_progspace and         gdb.events.free_progspace, these emit NewProgspaceEvent and          FreeProgspaceEvent event types respectively.  Both of these          event types have a single 'progspace' attribute, which is          the gdb.Progspace that is either being added to GDB, or          removed from GDB.
      * gdb.LazyString now implements the __str__ method.
      * New method gdb.Frame.static_link that returns the outer        frame of a nested function frame.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-984798 advisory.

    GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

According to the versions of the gdb packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack.(CVE-2022-48064)

Tenable has extracted the preceding description block directly from the EulerOS gdb security advisory.

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

According to the versions of the binutils package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a     DNS attack. (CVE-2022-48063)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

  - GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function     find_abstract_instance in dwarf2.c. (CVE-2022-48065)

  - A flaw was found in Binutils. The use of an uninitialized field in the struct module *module may lead to     application crash and local denial of service. (CVE-2023-25585)

  - MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in     zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported     part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected     zlib version, and exposes the applicable MiniZip code through its compress API. (CVE-2023-45853)

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

The remote Fedora 39 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2023-89ade611ee advisory.

    Backport upstream commit d28fbc7197b which fixes RHBZ 2233965, Security fix for CVE-2022-48065

    ----

    Security fix for CVE-2022-48064, Backport upstream commit 8f2c64de86b which fixes RHBZ 2233961,

Tenable has extracted the preceding description block directly from the Fedora security advisory.

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

According to the versions of the binutils package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37. (CVE-2021-46174)

  - An issue was discovered function stab_demangle_v3_arg in stabs.c in Binutils 2.34 thru 2.38, allows     attackers to cause a denial of service due to memory leaks. (CVE-2022-47007)

  - An issue was discovered function make_tempdir, and make_tempname in bucomm.c in Binutils 2.34 thru 2.38,     allows attackers to cause a denial of service due to memory leaks. (CVE-2022-47008)

  - An issue was discovered function pr_function_type in prdbg.c in Binutils 2.34 thru 2.38, allows attackers     to cause a denial of service due to memory leaks. (CVE-2022-47010)

  - An issue was discovered function parse_stab_struct_fields in stabs.c in Binutils 2.34 thru 2.38, allows     attackers to cause a denial of service due to memory leaks. (CVE-2022-47011)

  - An issue was discovered in Binutils addr2line before 2.39.3, function parse_module contains multiple out     of bound reads which may cause a denial of service or other unspecified impacts. (CVE-2022-47673)

  - An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or     other unspecified impacts via function bfd_mach_o_get_synthetic_symtab in match-o.c. (CVE-2022-47695)

  - An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or     other unspecified impacts via function compare_symbols. (CVE-2022-47696)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a     DNS attack. (CVE-2022-48063)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

  - GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function     find_abstract_instance in dwarf2.c. (CVE-2022-48065)

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

According to the versions of the binutils package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow     issue in demangle_type in rust-demangle.c. (CVE-2021-32256)

  - Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37. (CVE-2021-46174)

  - libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by     nm-new. (CVE-2022-27943)

  - Heap buffer overflow vulnerability in binutils readelf before 2.40 via function find_section_in_set in     file readelf.c. (CVE-2022-44840)

  - An issue was discovered function stab_demangle_v3_arg in stabs.c in Binutils 2.34 thru 2.38, allows     attackers to cause a denial of service due to memory leaks. (CVE-2022-47007)

  - An issue was discovered function make_tempdir, and make_tempname in bucomm.c in Binutils 2.34 thru 2.38,     allows attackers to cause a denial of service due to memory leaks. (CVE-2022-47008)

  - An issue was discovered function pr_function_type in prdbg.c in Binutils 2.34 thru 2.38, allows attackers     to cause a denial of service due to memory leaks. (CVE-2022-47010)

  - An issue was discovered function parse_stab_struct_fields in stabs.c in Binutils 2.34 thru 2.38, allows     attackers to cause a denial of service due to memory leaks. (CVE-2022-47011)

  - An issue was discovered in Binutils addr2line before 2.39.3, function parse_module contains multiple out     of bound reads which may cause a denial of service or other unspecified impacts. (CVE-2022-47673)

  - An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or     other unspecified impacts via function bfd_mach_o_get_synthetic_symtab in match-o.c. (CVE-2022-47695)

  - An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or     other unspecified impacts via function compare_symbols. (CVE-2022-47696)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a     DNS attack. (CVE-2022-48063)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

  - GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function     find_abstract_instance in dwarf2.c. (CVE-2022-48065)

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

According to the versions of the gdb packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

  - GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function     find_abstract_instance in dwarf2.c. (CVE-2022-48065)

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2024:4414-1 advisory.

    Mention changes in GDB 14:

    * GDB now supports the AArch64 Scalable Matrix Extension 2       (SME2), which includes a new 512 bit lookup table register       named ZT0.
    * GDB now supports the AArch64 Scalable Matrix Extension (SME),       which includes a new matrix register named ZA, a new thread       register TPIDR2 and a new vector length register SVG       (streaming vector granule).  GDB also supports tracking ZA       state across signal frames.  Some features are still under       development or are dependent on ABI specs that are still in       alpha stage.  For example, manual function calls with ZA state       don't have any special handling, and tracking of SVG changes       based on DWARF information is still not implemented, but there       are plans to do so in the future.
    * GDB now recognizes the NO_COLOR environment variable and       disables styling according to the spec.  See       https://no-color.org/.  Styling can be re-enabled with       'set style enabled on'.
    * The AArch64 'org.gnu.gdb.aarch64.pauth' Pointer Authentication       feature string has been deprecated in favor of the       'org.gnu.gdb.aarch64.pauth_v2' feature string.
    * GDB now has some support for integer types larger than 64 bits.
    * Multi-target feature configuration.
      GDB now supports the individual configuration of remote       targets' feature sets.  Based on the current selection of a       target, the commands 'set remote <name>-packet (on|off|auto)'       and 'show remote <name>-packet' can be used to configure a       target's feature packet and to display its configuration,       respectively.
    * GDB has initial built-in support for the Debugger Adapter       Protocol.
    * For the break command, multiple uses of the 'thread' or 'task'       keywords will now give an error instead of just using the       thread or task id from the last instance of the keyword.  E.g.:
        break foo thread 1 thread 2       will now give an error rather than using 'thread 2'.
    * For the watch command, multiple uses of the 'task' keyword will       now give an error instead of just using the task id from the       last instance of the keyword.  E.g.:
        watch my_var task 1 task 2       will now give an error rather than using 'task 2'.  The       'thread' keyword already gave an error when used multiple times       with the watch command, this remains unchanged.
    * The 'set print elements' setting now helps when printing large       arrays.  If an array would otherwise exceed max-value-size, but       'print elements' is set such that the size of elements to print       is less than or equal to 'max-value-size', GDB will now still       print the array, however only 'max-value-size' worth of data       will be added into the value history.
    * For both the break and watch commands, it is now invalid to use       both the 'thread' and 'task' keywords within the same command.
      For example the following commnds will now give an error:
        break foo thread 1 task 1         watch var thread 2 task 3
    * The printf command now accepts a '%V' output format which will       format an expression just as the 'print' command would.  Print       options can be placed withing '[...]' after the '%V' to modify       how the value is printed.  E.g:
        printf '%V', some_array         printf '%V[-array-indexes on]', some_array       will print the array without, or with array indexes included,       just as the array would be printed by the 'print' command.
      This functionality is also available for dprintf when       dprintf-style is 'gdb'.
    * When the printf command requires a string to be fetched from       the   inferior, GDB now uses the existing 'max-value-size'       setting to the limit the memory allocated within GDB.  The       default 'max-value-size' is 64k.  To print longer strings you       should increase 'max-value-size'.
    * The Ada 2022 Enum_Rep and Enum_Val attributes are now       supported.
    * The Ada 2022 target name symbol ('@') is now supported by the       Ada expression parser.
    * The 'list' command now accepts '.' as an argument, which tells       GDB to print the location around the point of execution within       the current frame.  If the inferior hasn't started yet, the       command will print around the beginning of the 'main' function.
    * Using the 'list' command with no arguments in a situation where       the command would attempt to list past the end of the file now       warns the user that the end of file has been reached, refers       the user to the newly added '.' argument
    * Breakpoints can now be inferior-specific.  This is similar to       the   existing thread-specific breakpoint support.  Breakpoint       conditions can include the 'inferior' keyword followed by an       inferior id (as displayed in the 'info inferiors' output).
      It is invalid to use the 'inferior' keyword with either the       'thread' or 'task' keywords when creating a breakpoint.
    * New convenience function '$_shell', to execute a shell command       and return the result.  This lets you run shell commands in       expressions.  Some examples:
       (gdb) p $_shell('true')        $1 = 0        (gdb) p $_shell('false')        $2 = 1        (gdb) break func if $_shell('some command') == 0
    * New commands:

      * set debug breakpoint on|off         show debug breakpoint         Print additional debug messages about breakpoint insertion         and removal.
      * maintenance print record-instruction [ N ]         Print the recorded information for a given instruction.  If N         is not given prints how GDB would undo the last instruction         executed.  If N is negative, prints how GDB would undo the         N-th previous instruction, and if N is positive, it prints         how GDB will redo the N-th following instruction.
      * maintenance info frame-unwinders         List the frame unwinders currently in effect, starting with         the highest priority.
      * maintenance wait-for-index-cache         Wait until all pending writes to the index cache have         completed.
      * set always-read-ctf on|off         show always-read-ctf         When off, CTF is only read if DWARF is not present.  When on,         CTF is read regardless of whether DWARF is present.  Off by         default.
      * info main         Get main symbol to identify entry point into program.
      * set tui mouse-events [on|off]         show tui mouse-events         When on (default), mouse clicks control the TUI and can be         accessed by Python extensions.  When off, mouse clicks are         handled by the terminal, enabling terminal-native text         selection.

    * MI changes:

      * MI version 1 has been removed.
      * mi now reports 'no-history' as a stop reason when hitting the         end of the reverse execution history.
      * When creating a thread-specific breakpoint using the '-p'         option, the -break-insert command would report the 'thread'         field twice in the reply.  The content of both fields was         always identical.  This has now been fixed; the 'thread'         field will be reported just once for thread-specific         breakpoints, or not at all for breakpoints without a thread         restriction.  The same is also true for the 'task' field of         an Ada task-specific breakpoint.
        * It is no longer possible to create a thread-specific         breakpoint for a thread that doesn't exist using         '-break-insert -p ID'.  Creating breakpoints for         non-existent threads is not allowed when using the CLI, that         the MI allowed it was a long standing bug, which has now         been fixed.
      * The '--simple-values' argument to the         '-stack-list-arguments','-stack-list-locals',         '-stack-list-variables', and '-var-list-children' commands now         takes reference types into account: that is, a value is now         considered simple if it is neither an array, structure, or         union, nor a reference to an array, structure, or union.
        (Previously all references were considered simple.)  Support         for this feature can be verified by using the         '-list-features' command, which should contain         'simple-values-ref-types'.
      * The -break-insert command now accepts a '-g thread-group-id'         option to allow for the creation of inferior-specific         breakpoints.
      * The bkpt tuple, which appears in breakpoint-created         notifications, and in the result of the -break-insert         command can now include an optional 'inferior' field for both         the main breakpoint, and each location, when the breakpoint         is inferior-specific.

    * Python API:

      * gdb.ThreadExitedEvent added.  Emits a ThreadEvent.
      * The gdb.unwinder.Unwinder.name attribute is now read-only.
      * The name argument passed to gdb.unwinder.Unwinder.__init__         must now be of type 'str' otherwise a TypeError will be         raised.
      * The gdb.unwinder.Unwinder.enabled attribute can now only         accept values of type 'bool'.  Changing this attribute will         now invalidate GDB's frame-cache, which means GDB will need         to rebuild its frame-cache when next required - either with,         or without the particular unwinder, depending on how         'enabled' was changed.
      * New methods added to the gdb.PendingFrame class.  These         methods have the same behaviour as the corresponding         methods on gdb.Frame.  The new methods are:
        * gdb.PendingFrame.name: Return the name for the frame's           function, or None.
        * gdb.PendingFrame.is_valid: Return True if the pending           frame object is valid.
        * gdb.PendingFrame.pc: Return the $pc register value for           this frame.
        * gdb.PendingFrame.language: Return a string containing the           language for this frame, or None.
        * gdb.PendingFrame.find_sal: Return a gdb.Symtab_and_line           object for the current location within the pending frame,           or None.
        * gdb.PendingFrame.block: Return a gdb.Block for the current           pending frame, or None.
        * gdb.PendingFrame.function: Return a gdb.Symbol for the           current pending frame, or None.
      * The frame-id passed to gdb.PendingFrame.create_unwind_info         can now use either an integer or a gdb.Value object for each         of its 'sp', 'pc', and 'special' attributes.
      * A new class gdb.unwinder.FrameId has been added.  Instances         of this class are constructed with 'sp' (stack-pointer) and         'pc' (program-counter) values, and can be used as the         frame-id when calling gdb.PendingFrame.create_unwind_info.
      * It is now no longer possible to sub-class the         gdb.disassembler.DisassemblerResult type.
      * The Disassembler API from the gdb.disassembler module has         been extended to include styling support:
        * The DisassemblerResult class can now be initialized with a           list of parts.  Each part represents part of the           disassembled instruction along with the associated style           information.  This list of parts can be accessed with the           new DisassemblerResult.parts property.
        * New constants gdb.disassembler.STYLE_* representing all the           different styles part of an instruction might have.
        * New methods DisassembleInfo.text_part and           DisassembleInfo.address_part which are used to create the           new styled parts of a disassembled instruction.
        * Changes are backwards compatible, the older API can still           be used to disassemble instructions without styling.
      * New function gdb.execute_mi(COMMAND, [ARG]...), that invokes         a GDB/MI command and returns the output as a Python         dictionary.
      * New function gdb.block_signals().  This returns a context         manager that blocks any signals that GDB needs to handle         itself.
      * New class gdb.Thread.  This is a subclass of threading.Thread         that calls gdb.block_signals in its 'start' method.
      * gdb.parse_and_eval now has a new 'global_context' parameter.
        This can be used to request that the parse only examine         global symbols.
      * gdb.Inferior now has a new 'arguments' attribute.  This holds         the command-line arguments to the inferior, if known.
      * gdb.Inferior now has a new 'main_name' attribute.  This holds         the name of the inferior's 'main', if known.
      * gdb.Inferior now has new methods 'clear_env', 'set_env', and         'unset_env'.  These can be used to modify the inferior's         environment before it is started.
      * gdb.Value now has the 'assign' method.
      * gdb.Value now has the 'to_array' method.  This converts an         array-like Value to an array.
      * gdb.Progspace now has the new method 'objfile_for_address'.
        This returns the gdb.Objfile, if any, that covers a given         address.
      * gdb.Breakpoint now has an 'inferior' attribute.  If the         Breakpoint object is inferior specific then this attribute         holds the inferior-id (an integer).  If the Breakpoint         object is not inferior specific, then this field contains         None.  This field can be written too.
      * gdb.Type now has the 'is_array_like' and 'is_string_like'         methods.  These reflect GDB's internal idea of whether a         type might be array- or string-like, even if they do not         have the corresponding type code.
      * gdb.ValuePrinter is a new class that can be used as the base         class for the result of applying a pretty-printer.  As a         base class, it signals to gdb that the printer may implement         new pretty-printer methods.
      * New attribute Progspace.symbol_file.  This attribute holds         the gdb.Objfile that corresponds to Progspace.filename (when         Progspace.filename is not None), otherwise, this attribute is         itself None.
      * New attribute Progspace.executable_filename.  This attribute         holds a string containing a file name set by the 'exec-file'         or 'file' commands, or None if no executable file is set.
        This isn't the exact string passed by the user to these         commands; the file name will have been partially resolved to         an absolute file name.
      * A new executable_changed event registry is available.  This         event emits ExecutableChangedEvent objects, which have         'progspace' (a gdb.Progspace) and 'reload' (a Boolean)         attributes.  This event is emitted when         gdb.Progspace.executable_filename changes.
      * New event registries gdb.events.new_progspace and         gdb.events.free_progspace, these emit NewProgspaceEvent and          FreeProgspaceEvent event types respectively.  Both of these          event types have a single 'progspace' attribute, which is          the gdb.Progspace that is either being added to GDB, or          removed from GDB.
      * gdb.LazyString now implements the __str__ method.
      * New method gdb.Frame.static_link that returns the outer        frame of a nested function frame.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The version of gdb installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2022-48064 advisory.

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

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

According to the versions of the binutils packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37. (CVE-2021-46174)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a     DNS attack. (CVE-2022-48063)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

  - GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function     find_abstract_instance in dwarf2.c. (CVE-2022-48065)

  - MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in     zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported     part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected     zlib version, and exposes the applicable MiniZip code through its compress API. (CVE-2023-45853)

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

According to the versions of the binutils packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37. (CVE-2021-46174)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a     DNS attack. (CVE-2022-48063)

  - GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the     function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file     and cause a DNS attack. (CVE-2022-48064)

  - GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function     find_abstract_instance in dwarf2.c. (CVE-2022-48065)

  - MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in     zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported     part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected     zlib version, and exposes the applicable MiniZip code through its compress API. (CVE-2023-45853)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
192139	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : gdb (SUSE-SU-2024:0898-1)	Nessus	SuSE Local Security Checks	2024/3/15	2024/3/15	high
203643	Photon OS 5.0: Binutils PHSA-2023-5.0-0096	Nessus	PhotonOS Local Security Checks	2024/7/23	2024/7/23	medium
203776	Photon OS 3.0: Binutils PHSA-2023-3.0-0655	Nessus	PhotonOS Local Security Checks	2024/7/24	2024/7/24	medium
213380	SUSE SLES15 Security Update : gdb (SUSE-SU-2024:4413-1)	Nessus	SuSE Local Security Checks	2024/12/24	2024/12/24	medium
267753	Unity Linux 20.1070e Security Update: gdb (UTSA-2025-984798)	Nessus	Unity Linux Local Security Checks	2025/10/7	2025/10/10	medium
271343	EulerOS 2.0 SP13 : gdb (EulerOS-SA-2025-2254)	Nessus	Huawei Local Security Checks	2025/10/24	2025/10/24	medium
274909	EulerOS 2.0 SP12 : gdb (EulerOS-SA-2025-2352)	Nessus	Huawei Local Security Checks	2025/11/12	2025/11/12	medium
188982	EulerOS Virtualization 2.9.1 : binutils (EulerOS-SA-2024-1029)	Nessus	Huawei Local Security Checks	2024/1/16	2024/1/16	critical
185258	Fedora 39 : gdb (2023-89ade611ee)	Nessus	Fedora Local Security Checks	2023/11/7	2024/11/14	medium
188820	EulerOS 2.0 SP10 : binutils (EulerOS-SA-2023-3200)	Nessus	Huawei Local Security Checks	2024/1/16	2024/1/16	high
188899	EulerOS Virtualization 2.11.0 : binutils (EulerOS-SA-2023-3373)	Nessus	Huawei Local Security Checks	2024/1/16	2024/1/16	high
191832	EulerOS 2.0 SP8 : gdb (EulerOS-SA-2024-1266)	Nessus	Huawei Local Security Checks	2024/3/12	2024/3/12	medium
213379	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : gdb (SUSE-SU-2024:4414-1)	Nessus	SuSE Local Security Checks	2024/12/24	2024/12/24	medium
234115	CBL Mariner 2.0 Security Update: gdb (CVE-2022-48064)	Nessus	MarinerOS Local Security Checks	2025/4/10	2025/4/10	medium
270020	EulerOS 2.0 SP11 : gdb (EulerOS-SA-2025-2190)	Nessus	Huawei Local Security Checks	2025/10/11	2025/10/11	medium
191865	EulerOS 2.0 SP8 : binutils (EulerOS-SA-2024-1257)	Nessus	Huawei Local Security Checks	2024/3/12	2024/3/12	critical
197230	EulerOS Virtualization 3.0.6.0 : binutils (EulerOS-SA-2024-1674)	Nessus	Huawei Local Security Checks	2024/5/17	2024/5/17	critical

检测

插件搜索

high

medium

medium

medium

medium

medium

medium

critical

medium

high

high

medium

medium

medium

medium

critical

critical