ghsa-pr44-4jfr-286m
Vulnerability from github
Published
2022-05-17 00:27
Modified
2024-04-24 22:03
Severity ?
Summary
Swift Mailer mail transport Command Injection
Details

The mail transport (aka Swift_Transport_MailTransport) in Swift Mailer before 5.4.5 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \" (backslash double quote) in a crafted e-mail address in the (1) From, (2) ReturnPath, or (3) Sender header.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "Packagist",
            name: "swiftmailer/swiftmailer",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "5.4.5",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2016-10074",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-77",
      ],
      github_reviewed: true,
      github_reviewed_at: "2024-04-24T22:03:23Z",
      nvd_published_at: "2016-12-30T19:59:00Z",
      severity: "CRITICAL",
   },
   details: "The mail transport (aka Swift_Transport_MailTransport) in Swift Mailer before 5.4.5 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \\\" (backslash double quote) in a crafted e-mail address in the (1) From, (2) ReturnPath, or (3) Sender header.",
   id: "GHSA-pr44-4jfr-286m",
   modified: "2024-04-24T22:03:24Z",
   published: "2022-05-17T00:27:49Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2016-10074",
      },
      {
         type: "WEB",
         url: "https://github.com/FriendsOfPHP/security-advisories/blob/master/swiftmailer/swiftmailer/CVE-2016-10074.yaml",
      },
      {
         type: "WEB",
         url: "https://github.com/swiftmailer/swiftmailer/blob/5.x/CHANGES",
      },
      {
         type: "WEB",
         url: "https://legalhackers.com/advisories/SwiftMailer-Exploit-Remote-Code-Exec-CVE-2016-10074-Vuln.html",
      },
      {
         type: "WEB",
         url: "https://www.exploit-db.com/exploits/40972",
      },
      {
         type: "WEB",
         url: "https://www.exploit-db.com/exploits/40986",
      },
      {
         type: "WEB",
         url: "https://www.exploit-db.com/exploits/42221",
      },
      {
         type: "WEB",
         url: "http://packetstormsecurity.com/files/140290/SwiftMailer-Remote-Code-Execution.html",
      },
      {
         type: "WEB",
         url: "http://seclists.org/fulldisclosure/2016/Dec/86",
      },
      {
         type: "WEB",
         url: "http://www.debian.org/security/2017/dsa-3769",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/95140",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "Swift Mailer mail transport Command Injection",
}


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.