Skip to content
Threat Brief

← All advisories

CVE-2023-2868

Critical 9.4KEV · exploitedFix available

Remote Code injection in Barracuda Email Security Gateway

Record last updated

CVSS score

9.4

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

87%

Among the highest-scored CVEs. A prediction, not evidence.

CISA remediation deadline

1254days overdue

Passed 1254 days ago for U.S. federal agencies

Description

A remote command injection vulnerability exists in the Barracuda Email Security Gateway (appliance form factor only) product effecting versions 5.1.3.001-9.2.0.006. The vulnerability arises out of a failure to comprehensively sanitize the processing of .tar file (tape archives). The vulnerability stems from incomplete input validation of a user-supplied .tar file as it pertains to the names of the files contained within the archive. As a consequence, a remote attacker can specifically format these file names in a particular manner that will result in remotely executing a system command through Perl's qx operator with the privileges of the Email Security Gateway product. This issue was fixed as part of BNSF-36456 patch. This patch was automatically applied to all customer appliances.

Weakness: CWE-20

Patching and mitigation

Patch status
Fix available (source: CVE record (Google))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
status.barracuda.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
BarracudaBarracuda Email Security Gatewayfrom 5.1.3.001 before 9.2.0.0069.2.0.006CVE Program
Barracuda NetworksEmail Security Gateway (ESG) ApplianceNot documentedNot documentedCISA KEV

Timeline

  1. Disclosure

    CVE record published by Google

    Source: CVE Program (opens in a new tab)

  2. 26 May 2023KEV

    Added to the CISA Known Exploited Vulnerabilities catalog

    Source: CISA KEV (opens in a new tab)

  3. 26 May 2023Exploitation

    Exploitation confirmed by CISA KEV

    Source: CISA KEV (opens in a new tab)

  4. Patch

    Fix documented by CVE record (Google)

    Source: CVE record (Google) (opens in a new tab)

Vendor guidance and references