dbcve.org
Email Security Gateway 300 FirmwareOperating system · Barracuda

CVE-2023-7102

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-24
Fix available
A fix is available. Upgrade to after 9.2.1.001 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of a Third Party library produced a vulnerability in Barracuda Networks Inc. Barracuda ESG Appliance which allowed Parameter Injection.This issue affected Barracuda ESG Appliance, from 5.1.3.001 through 9.2.1.001, until Barracuda removed the vulnerable logic.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A parameter injection vulnerability existed in Barracuda ESG Appliance versions 5.1.3.001 through 9.2.1.001 due to the use of a vulnerable third-party library. The vulnerability allowed attackers to manipulate parameters to inject malicious input, potentially leading to unauthorized access or command execution.

MitigationUpgrade Barracuda ESG Appliance to a version beyond 9.2.1.001 where Barracuda has removed the vulnerable third-party library logic, or apply the vendor-supplied patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Email Security Gateway 300 FirmwareOperating system
Affected:>= 5.1.3.001, <= 9.2.1.001
Email Security Gateway 400 FirmwareOperating system
Affected:>= 5.1.3.001, <= 9.2.1.001
Email Security Gateway 600 FirmwareOperating system
Affected:>= 5.1.3.001, <= 9.2.1.001
Email Security Gateway 800 FirmwareOperating system
Affected:>= 5.1.3.001, <= 9.2.1.001
Email Security Gateway 900 FirmwareOperating system
Affected:>= 5.1.3.001, <= 9.2.1.001

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ESG model number
    Locate the model label on the physical appliance or check the web interface for the model identifier (300, 400, 600, 800, or 900)
    Affected if The model is one of the five affected ESG models (300, 400, 600, 800, 900)
  2. Check the installed firmware version
    Access the ESG web administration console and navigate to the System Info or About page, or use the CLI command 'system version' or 'show version' to retrieve the firmware build number
    Affected if The firmware version falls within the range 5.1.3.001 to 9.2.1.001 inclusive
  3. Confirm the third-party library is present
    Inspect the appliance file system via CLI (if administrative access is available) for the vulnerable library components referenced in the CVE documentation
    Affected if The vulnerable third-party library files exist on the appliance filesystem within the affected version range
  4. Review access logs for parameter manipulation
    Examine the ESG access logs or web logs for suspicious parameter patterns in HTTP requests, particularly unusual characters or commands embedded in query parameters
    Affected if Logs show unexpected parameter values or injection attempts targeting web interface parameters

The environment is affected if the ESG firmware version is between 5.1.3.001 and 9.2.1.001 inclusive on any of the five affected models (300, 400, 600, 800, 900).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.2.1.001
Interim mitigation

Upgrade Barracuda ESG Appliance to a version beyond 9.2.1.001 where Barracuda has removed the vulnerable third-party library logic, or apply the vendor-supplied patch.

Recommended fix Moderate confidence

Firmware version > 9.2.1.001 (any newer version released by Barracuda that removes the vulnerable third-party library component)

  1. 1. Identify the current firmware version of the Barracuda ESG Appliance by accessing the admin console or using the device's web interface.
  2. 2. Navigate to the firmware update or system upgrade section in the admin panel.
  3. 3. Check for available firmware updates. Versions greater than 9.2.1.001 contain the fix for CVE-2023-7102.
  4. 4. Download and apply the latest available firmware version from Barracuda's official support portal.
  5. 5. After upgrade, verify the device is running a firmware version above 9.2.1.001 and confirm normal operation of email security functions.
Caveat Review Barracuda release notes for the target version to check for any functionality changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Email Security Gateway 300 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-7102 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data