Security Resilience

CVE-2017-6320

RCE in Barracuda Load Balancer Adc Firmware ≤ 6.0.1.006

Published
18 July 2017
Modified
12 November 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.11 96th percentile
Risk Priority 79 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2017-6320 is a high-severity OS Command Injection (CWE-78) vulnerability in Barracuda Load Balancer Adc Firmware. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

stems from unsanitized data being processed in a system call when the delete_assessment command is issued.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
T1584.004 Server Resource Development
Adversaries may compromise third-party servers that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26213Same vendor: Barracuda
CVE-2023-50214Shared CWE-78
CVE-2026-25721Shared CWE-78
CVE-2014-3008Shared CWE-78
CVE-2024-30414Shared CWE-78
CVE-2018-11183Shared CWE-78
CVE-2017-14135Shared CWE-78
CVE-2024-50360Shared CWE-78
CVE-2025-34134Shared CWE-78
CVE-2026-1427Shared CWE-78

Affected Assets

barracuda
load balancer adc firmware
≤ 6.0.1.006

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover missing or incorrect command sanitization during development.

Secure engineering principles require proper neutralization of untrusted input before command construction.

Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.

PR.PS-02 partial match
blocks

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

prevents

Training helps developers understand the risks of unsafe OS command construction and the need for input neutralization, but general awareness training is fallible and less directly applicable than dedicated secure coding practice (A.8.28, graded `partial` against XSS); most OS command injection instances arise from implementation mistakes that awareness alone does not prevent.

prevents

A.8.28 mandates secure coding practices (input validation, avoiding dangerous functions like system()/exec(), peer review, SAST during development) that prevent some OS command injection instances, but it is a practice-based control whose effect depends on developer skill and implementation rigor, leaving a fallible remainder that A.8.29 testing reaches more completely.

prevents

A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software CWEs like OS command injection in delivered code the way those practices do, but the effect is mediated by the supplier's implementation and is not complete.

finds

A.8.8's reach is DISCLOSURE — it finds OS command injection only where it has been published as a CVE in a third-party component, which is a minority of instances; most CWE-78 lives in first-party code that A.8.8's published-advisory and component-inventory programme does not read.

References