fkie_cve-2022-1834
Vulnerability from fkie_nvd
Published
2022-12-22 20:15
Modified
2024-11-21 06:41
Summary
When displaying the sender of an email, and the sender name contained the Braille Pattern Blank space character multiple times, Thunderbird would have displayed all the spaces. This could have been used by an attacker to send an email message with the attacker's digital signature, that was shown with an arbitrary sender email address chosen by the attacker. If the sender name started with a false email address, followed by many Braille space characters, the attacker's email address was not visible. Because Thunderbird compared the invisible sender address with the signature's email address, if the signing key or certificate was accepted by Thunderbird, the email was shown as having a valid digital signature. This vulnerability affects Thunderbird < 91.10.
Impacted products
Vendor Product Version
mozilla thunderbird *



{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:mozilla:thunderbird:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "4A62DB30-D938-4ADD-BF43-9BBC56A6B8C0",
                     versionEndExcluding: "91.10",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "When displaying the sender of an email, and the sender name contained the Braille Pattern Blank space character multiple times, Thunderbird would have displayed all the spaces. This could have been used by an attacker to send an email message with the attacker's digital signature, that was shown with an arbitrary sender email address chosen by the attacker. If the sender name started with a false email address, followed by many Braille space characters, the attacker's email address was not visible. Because Thunderbird compared the invisible sender address with the signature's email address, if the signing key or certificate was accepted by Thunderbird, the email was shown as having a valid digital signature. This vulnerability affects Thunderbird < 91.10.",
      },
      {
         lang: "es",
         value: "Al mostrar el remitente de un correo electrónico y el nombre del remitente contenía el carácter de espacio en blanco del patrón Braille varias veces, Thunderbird habría mostrado todos los espacios. Un atacante podría haberlo utilizado para enviar un mensaje de correo electrónico con su firma digital, que se mostraba con una dirección de correo electrónico de remitente arbitraria elegida por el atacante. Si el nombre del remitente comenzaba con una dirección de correo electrónico falsa, seguida de muchos caracteres de espacio en Braille, la dirección de correo electrónico del atacante no era visible. Debido a que Thunderbird comparó la dirección del remitente invisible con la dirección de correo electrónico de la firma, si Thunderbird aceptaba la clave de firma o el certificado, se mostraba que el correo electrónico tenía una firma digital válida. Esta vulnerabilidad afecta a Thunderbird &lt; 91.10.",
      },
   ],
   id: "CVE-2022-1834",
   lastModified: "2024-11-21T06:41:34.397",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 6.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "HIGH",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 3.6,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2022-12-22T20:15:13.513",
   references: [
      {
         source: "security@mozilla.org",
         tags: [
            "Issue Tracking",
            "Permissions Required",
            "Vendor Advisory",
         ],
         url: "https://bugzilla.mozilla.org/show_bug.cgi?id=1767816",
      },
      {
         source: "security@mozilla.org",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://www.mozilla.org/security/advisories/mfsa2022-22/",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Issue Tracking",
            "Permissions Required",
            "Vendor Advisory",
         ],
         url: "https://bugzilla.mozilla.org/show_bug.cgi?id=1767816",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://www.mozilla.org/security/advisories/mfsa2022-22/",
      },
   ],
   sourceIdentifier: "security@mozilla.org",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-295",
            },
         ],
         source: "nvd@nist.gov",
         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.


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.