fkie_cve-2023-24011
Vulnerability from fkie_nvd
Published
2025-01-09 15:15
Modified
2025-01-09 16:15
Summary
An attacker can arbitrarily craft malicious DDS Participants (or ROS 2 Nodes) with valid certificates to compromise and get full control of the attacked secure DDS databus system by exploiting vulnerable attributes in the configuration of PKCS#7 certificate’s validation. This is caused by a non-compliant implementation of permission document verification used by some DDS vendors. Specifically, an improper use of the OpenSSL PKCS7_verify function used to validate S/MIME signatures.
Impacted products
Vendor Product Version



{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "An attacker can arbitrarily craft malicious DDS Participants (or ROS 2 Nodes) with valid certificates to compromise and get full control of the attacked secure DDS databus system by exploiting vulnerable attributes in the configuration of PKCS#7 certificate’s validation. This is caused by a non-compliant implementation of permission document verification used by some DDS vendors. Specifically, an improper use of the OpenSSL PKCS7_verify function used to validate S/MIME signatures.",
      },
      {
         lang: "es",
         value: "Un atacante puede manipular de forma arbitraria participantes maliciosos de DDS (o nodos ROS 2) con certificados válidos para comprometer y obtener el control total del sistema de bus de datos DDS seguro atacado explotando atributos vulnerables en la configuración de validación del certificado PKCS#7. Esto se debe a una implementación no conforme de la verificación de documentos de permiso utilizada por algunos proveedores de DDS. En concreto, un uso indebido de la función PKCS7_verify de OpenSSL utilizada para validar firmas S/MIME.",
      },
   ],
   id: "CVE-2023-24011",
   lastModified: "2025-01-09T16:15:31.323",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "LOW",
               baseScore: 8.2,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L",
               version: "3.1",
            },
            exploitabilityScore: 3.9,
            impactScore: 4.2,
            source: "cve-coordination@incibe.es",
            type: "Secondary",
         },
      ],
   },
   published: "2025-01-09T15:15:11.657",
   references: [
      {
         source: "cve-coordination@incibe.es",
         url: "https://gist.github.com/vmayoral/235c02d0b0ef85a29812eff6980ff80d",
      },
      {
         source: "cve-coordination@incibe.es",
         url: "https://github.com/ros2/sros2/issues/282",
      },
      {
         source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
         url: "https://gist.github.com/vmayoral/235c02d0b0ef85a29812eff6980ff80d",
      },
   ],
   sourceIdentifier: "cve-coordination@incibe.es",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-200",
            },
         ],
         source: "cve-coordination@incibe.es",
         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.


Loading…

Loading…

Loading…

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.