LiveActive security incident?Get immediate response
CVE Record

CVE-2017-6320: A remote command injection vulnerability exists in the Barracuda Load Balancer product line (confirmed on v...

A remote command injection vulnerability exists in the Barracuda Load Balancer product line (confirmed on v5.4.0.004 (2015-11-26) and v6.0.1.006 (2016-08-19); fixed in 6.1.0.003 (2017-01-17)) in which an authenticated user can execute arbitrary shell commands and gain root privileges. The vulnerability stems from unsanitized data being processed in a system call when the delete_assessment command is issued.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-6320 lets an authenticated user on Barracuda Load Balancer execute operating-system commands and obtain root privileges. For executives, this means a valid or stolen admin-level path into an affected appliance could become full device compromise. Sources identify fixes in version 6.1.0.003; no KEV listing is provided.

Executive priority

Treat this as a high-priority legacy appliance issue. Full root compromise of a load balancer can affect traffic handling and security controls. Prioritize version verification, upgrade planning, and administrative access review, especially for internet-reachable or broadly accessible management interfaces.

Technical view

The flaw is a remote command injection in Barracuda Load Balancer, confirmed on 5.4.0.004 and 6.0.1.006. Unsanitized data reaches a system call when the delete_assessment command is issued, allowing arbitrary shell command execution as root by an authenticated user. The CVE states it was fixed in 6.1.0.003.

Likely exposure

Exposure is most likely in organizations still running legacy Barracuda Load Balancer versions 5.4.0.004 or 6.0.1.006, especially where management access is reachable by many administrators or external networks. The provided metadata does not list complete affected CPEs or all impacted versions.

Exploitation context

An Exploit-DB reference exists, indicating public exploit information was published. The bundle does not show CISA KEV listing or confirmed active exploitation. Authentication is required, so risk increases with weak credentials, shared admin accounts, exposed management interfaces, or compromised operator access.

Researcher notes

The strongest evidence is the CVE description: authenticated command injection, root impact, confirmed vulnerable versions, and fixed version. Severity scoring, complete affected product metadata, and active exploitation evidence are not present in the bundle. Avoid assuming unauthenticated exploitation or broader Barracuda product impact.

Mitigation direction

  • Upgrade affected Barracuda Load Balancer systems to 6.1.0.003 or later.
  • Review Barracuda release notes and support guidance for the correct upgrade path.
  • Restrict management interface access to trusted administrative networks only.
  • Remove unnecessary administrative accounts and rotate credentials for active administrators.
  • Investigate unsupported or end-of-life appliances for replacement or isolation.

Validation and detection

  • Inventory Barracuda Load Balancer instances and record running firmware versions.
  • Confirm no systems remain on 5.4.0.004 or 6.0.1.006.
  • Check whether management interfaces are reachable from untrusted networks.
  • Review administrative logs for unusual authenticated activity or configuration changes.
  • Verify the vendor-fixed version is deployed after maintenance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-6320 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.