fkie_cve-2025-0690
Vulnerability from fkie_nvd
Published
2025-02-24 08:15
Modified
2025-03-05 21:15
Severity ?
6.1 (Medium) - CVSS:3.1/AV:P/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Summary
The read command is used to read the keyboard input from the user, while reads it keeps the input length in a 32-bit integer value which is further used to reallocate the line buffer to accept the next character. During this process, with a line big enough it's possible to make this variable to overflow leading to a out-of-bounds write in the heap based buffer. This flaw may be leveraged to corrupt grub's internal critical data and secure boot bypass is not discarded as consequence.
References
secalert@redhat.comhttps://access.redhat.com/security/cve/CVE-2025-0690
secalert@redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2346123
secalert@redhat.comhttps://lists.gnu.org/archive/html/grub-devel/2025-02/msg00024.html
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "The read command is used to read the keyboard input from the user, while reads it keeps the input length in a 32-bit integer value which is further used to reallocate the line buffer to accept the next character. During this process, with a line big enough it's possible to make this variable to overflow leading to a out-of-bounds write in the heap based buffer. This flaw may be leveraged to corrupt grub's internal critical data and secure boot bypass is not discarded as consequence.",
      },
      {
         lang: "es",
         value: " El comando read se utiliza para leer la entrada del teclado del usuario, mientras que reads mantiene la longitud de la entrada en un valor entero de 32 bits que se utiliza para reasignar el búfer de línea para aceptar el siguiente carácter. Durante este proceso, con una línea lo suficientemente grande es posible hacer que esta variable se desborde, lo que lleva a una escritura fuera de los límites en el búfer basado en el montón. Este fallo puede aprovecharse para corromper los datos críticos internos de grub y la omisión del arranque seguro no se descarta como consecuencia.",
      },
   ],
   id: "CVE-2025-0690",
   lastModified: "2025-03-05T21:15:19.603",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "PHYSICAL",
               availabilityImpact: "HIGH",
               baseScore: 6.1,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "HIGH",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:P/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 0.2,
            impactScore: 5.9,
            source: "secalert@redhat.com",
            type: "Secondary",
         },
      ],
   },
   published: "2025-02-24T08:15:09.503",
   references: [
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/security/cve/CVE-2025-0690",
      },
      {
         source: "secalert@redhat.com",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=2346123",
      },
      {
         source: "secalert@redhat.com",
         url: "https://lists.gnu.org/archive/html/grub-devel/2025-02/msg00024.html",
      },
   ],
   sourceIdentifier: "secalert@redhat.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-787",
            },
         ],
         source: "secalert@redhat.com",
         type: "Secondary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.