LiveActive security incident?Get immediate response
CVE Record

CVE-2020-13377: The web-services interface of Loadbalancer.org Enterprise VA MAX through 8.3.8 could allow an authenticated...

The web-services interface of Loadbalancer.org Enterprise VA MAX through 8.3.8 could allow an authenticated, remote, low-privileged attacker to conduct directory traversal attacks and obtain read and write access to sensitive files.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-13377 is a high-severity path traversal issue in Loadbalancer.org Enterprise VA MAX through 8.3.8. A logged-in, low-privileged remote user could use the web-services interface to read and write sensitive files, creating confidentiality and integrity risk on affected load balancer appliances.

Executive priority

Treat as a priority remediation for affected load balancer appliances. The issue can expose or alter sensitive files after authentication, so the main business risk is compromise of infrastructure configuration or secrets by any user with appliance access.

Technical view

The issue is CWE-22 directory traversal in the web-services interface. The CVSS 3.1 score is 8.1 with network access, low complexity, low privileges, no user interaction, and high confidentiality and integrity impact. Availability impact is not listed.

Likely exposure

Exposure appears limited to Loadbalancer.org Enterprise VA MAX deployments through version 8.3.8 where the web-services interface is reachable and low-privileged authenticated accounts exist. The source bundle does not identify other affected products or CPEs.

Exploitation context

CISA KEV status is false in the provided bundle. The cited description supports authenticated remote exploitation by a low-privileged user, but the bundle does not support claims of active exploitation in the wild.

Researcher notes

The bundle provides high-level vulnerability details but not a vendor advisory, fixed version, or supported workaround. Avoid assuming a specific patch. Validate exposure by product, version, interface reachability, and account model, then align remediation with Loadbalancer.org guidance.

Mitigation direction

  • Inventory Enterprise VA MAX appliances and identify versions through 8.3.8.
  • Check Loadbalancer.org guidance for the supported fix or upgrade path.
  • Restrict web-services interface access to trusted administrative networks.
  • Review and reduce low-privileged accounts with appliance access.
  • Monitor for unexpected sensitive file reads or writes.

Validation and detection

  • Confirm appliance version and whether it is through 8.3.8.
  • Verify the web-services interface is not publicly reachable.
  • Review account lists for unnecessary low-privileged users.
  • Check appliance logs for unusual authenticated web-services activity.
  • Confirm remediation status against vendor guidance.
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.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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-2020-13377 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2020-13377Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.