fkie_cve-2025-27809
Vulnerability from fkie_nvd
Published
2025-03-25 06:15
Modified
2025-03-27 16:45
Severity ?
5.4 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Summary
Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname.
References
cve@mitre.orghttps://github.com/Mbed-TLS/mbedtls/releases
cve@mitre.orghttps://mbed-tls.readthedocs.io/en/latest/security-advisories/mbedtls-security-advisory-2025-03-1/
af854a3a-2127-422b-91ae-364da2661108https://github.com/Mbed-TLS/mbedtls/issues/466
af854a3a-2127-422b-91ae-364da2661108https://mastodon.social/@bagder/114219540623402700
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname.",
      },
      {
         lang: "es",
         value: "Mbed TLS anterior a 2.28.10 y 3.x anterior a 3.6.3, en el lado del cliente, acepta servidores que tienen certificados confiables para nombres de host arbitrarios a menos que la aplicación cliente TLS llame a mbedtls_ssl_set_hostname.",
      },
   ],
   id: "CVE-2025-27809",
   lastModified: "2025-03-27T16:45:46.410",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 5.4,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "CHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.2,
            impactScore: 2.7,
            source: "cve@mitre.org",
            type: "Secondary",
         },
      ],
   },
   published: "2025-03-25T06:15:41.000",
   references: [
      {
         source: "cve@mitre.org",
         url: "https://github.com/Mbed-TLS/mbedtls/releases",
      },
      {
         source: "cve@mitre.org",
         url: "https://mbed-tls.readthedocs.io/en/latest/security-advisories/mbedtls-security-advisory-2025-03-1/",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://github.com/Mbed-TLS/mbedtls/issues/466",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://mastodon.social/@bagder/114219540623402700",
      },
   ],
   sourceIdentifier: "cve@mitre.org",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-1188",
            },
         ],
         source: "cve@mitre.org",
         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.