CVE-2023-2868
CVE-2023-2868 — Barracuda Networks ESG Appliance Improper Input Validation Vulnerability
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.
Published Updated Sources: NVD, CISA, FIRST EPSS
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed May 26, 2023
EPSS
87%
ahead of 99.7% of scored CVEs
CVSS base
9.8
critical · 2 sources
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade barracuda_email_security_gateway to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply updates per vendor instructions.
Federal deadline Jun 16, 2023 — passed 1,185 days ago
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| barracuda | barracuda_email_security_gateway | — | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 9.4 | CVSS 3.1 | critical | 3.9 | 5.5 | google.com (CNA) |
| 9.8 | CVSS 3.1 | critical | 3.9 | 5.9 | NVD |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Weakness & attack patterns
- CWE-20Improper Input Validation
- CWE-77Command Injection
Inferred from the weakness class — not observed against this CVE.
- T1562.003Impair Defenses: Impair Command History Logging
- T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
May 26, 2023
Federal deadline
Jun 16, 2023
passed 1,185 days ago
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Exploit entries
1
Exploit-DB and CTI exploit indexes
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable barracuda_email_security_gateway.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
- 2023
Added to CISA KEV catalog
May 26, 2023 · CISA
Initial · CVE published
May 24, 2023 · NVD
References
4 on the record
- status.barracuda.com/incidents/34kx82j5n4q9
Vendor Advisory
- www.barracuda.com/company/legal/esg-vulnerability
Mitigation, Vendor Advisory
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-2868
US Government Resource
- nvd.nist.gov/vuln/detail/CVE-2023-2868
Vendor Advisory
Elsewhere on this site
- barracudaevery CVE for this vendor
- May 2023what else CISA listed
- Remote Code Execsame class
- CWE-20other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2023-2868 is Barracuda Networks ESG Appliance Improper Input Validation Vulnerability, a critical vulnerability affecting barracuda_email_security_gateway from barracuda. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 87% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.