cve.bz

CVE-2023-42130 a10networks advanced core operating system: Path traversal

8.8 highExploit referenceEPSS 2.1%

High (8.8) in a10networks advanced core operating system. EPSS 2.1% estimated probability of exploitation activity in the next 30 days.

On this page
A10 Thunder ADC FileMgmtExport Directory Traversal Arbitrary File Read and Deletion Vulnerability. This vulnerability allows remote attackers to read and delete arbitrary files on affected installations of A10 Thunder ADC. Authentication is required to exploit this vulnerability. The specific flaw exists within the FileMgmtExport class. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to read and delete files in the context of the service account. . Was ZDI-CAN-17905.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
2.1% (unchanged from 2.1% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 83rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-06-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-42130 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-42130?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-42130?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-42130 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
a10networks:advanced_core_operating_systemfrom 5.1.0 before 5.2.1
a10networks:advanced_core_operating_systemfrom 6.0.0 before 6.0.2
a10networks:advanced_core_operating_system4.1.4
a10networks:advanced_core_operating_system4.1.4:gr1
a10networks:advanced_core_operating_system4.1.4:gr1-p1
a10networks:advanced_core_operating_system4.1.4:gr1-p10
a10networks:advanced_core_operating_system4.1.4:gr1-p11
a10networks:advanced_core_operating_system4.1.4:gr1-p12
a10networks:advanced_core_operating_system4.1.4:gr1-p13
a10networks:advanced_core_operating_system4.1.4:gr1-p14
a10networks:advanced_core_operating_system4.1.4:gr1-p2
a10networks:advanced_core_operating_system4.1.4:gr1-p3
a10networks:advanced_core_operating_system4.1.4:gr1-p4
a10networks:advanced_core_operating_system4.1.4:gr1-p5
a10networks:advanced_core_operating_system4.1.4:gr1-p6
a10networks:advanced_core_operating_system4.1.4:gr1-p7
a10networks:advanced_core_operating_system4.1.4:gr1-p8
a10networks:advanced_core_operating_system4.1.4:gr1-p9
a10networks:advanced_core_operating_system5.2.1
a10networks:advanced_core_operating_system5.2.1:p1
a10networks:advanced_core_operating_system5.2.1:p2
a10networks:advanced_core_operating_system5.2.1:p3
a10networks:advanced_core_operating_system5.2.1:p4
a10networks:advanced_core_operating_system5.2.1:p5
a10networks:advanced_core_operating_system5.2.1:p6
a10networks:advanced_core_operating_system5.2.1:p7
a10networks:advanced_core_operating_system5.2.1:p8
a10networks:advanced_core_operating_system5.2.1:p9

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON