fkie_cve-2025-24912
Vulnerability from fkie_nvd
Published
2025-03-12 05:15
Modified
2025-03-12 05:15
Severity ?
3.7 (Low) - CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Summary
hostapd fails to process crafted RADIUS packets properly. When hostapd authenticates wi-fi devices with RADIUS authentication, an attacker in the position between the hostapd and the RADIUS server may inject crafted RADIUS packets and force RADIUS authentications to fail.
References
vultures@jpcert.or.jphttps://jvn.jp/en/jp/JVN19358384/
vultures@jpcert.or.jphttps://w1.fi/cgit/hostap/commit/?id=339a334551ca911187cc870f4f97ef08e11db109
vultures@jpcert.or.jphttps://w1.fi/cgit/hostap/commit/?id=726432d7622cc0088ac353d073b59628b590ea44
vultures@jpcert.or.jphttps://w1.fi/hostapd/
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "hostapd fails to process crafted RADIUS packets properly. When hostapd authenticates wi-fi devices with RADIUS authentication, an attacker in the position between the hostapd and the RADIUS server may inject crafted RADIUS packets and force RADIUS authentications to fail.",
      },
      {
         lang: "es",
         value: "hostapd no procesa correctamente los paquetes RADIUS manipulados. Cuando hostapd autentica dispositivos Wi-Fi con autenticación RADIUS, un atacante ubicado entre hostapd y el servidor RADIUS podría inyectar paquetes RADIUS manipulados y forzar el fallo de las autenticaciones RADIUS.",
      },
   ],
   id: "CVE-2025-24912",
   lastModified: "2025-03-12T05:15:37.430",
   metrics: {
      cvssMetricV30: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "LOW",
               baseScore: 3.7,
               baseSeverity: "LOW",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
               version: "3.0",
            },
            exploitabilityScore: 2.2,
            impactScore: 1.4,
            source: "vultures@jpcert.or.jp",
            type: "Secondary",
         },
      ],
   },
   published: "2025-03-12T05:15:37.430",
   references: [
      {
         source: "vultures@jpcert.or.jp",
         url: "https://jvn.jp/en/jp/JVN19358384/",
      },
      {
         source: "vultures@jpcert.or.jp",
         url: "https://w1.fi/cgit/hostap/commit/?id=339a334551ca911187cc870f4f97ef08e11db109",
      },
      {
         source: "vultures@jpcert.or.jp",
         url: "https://w1.fi/cgit/hostap/commit/?id=726432d7622cc0088ac353d073b59628b590ea44",
      },
      {
         source: "vultures@jpcert.or.jp",
         url: "https://w1.fi/hostapd/",
      },
   ],
   sourceIdentifier: "vultures@jpcert.or.jp",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-826",
            },
         ],
         source: "vultures@jpcert.or.jp",
         type: "Primary",
      },
   ],
}


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.