cve.bz

CVE-2023-34982 aveva: External Control of File Name or Path

7.1 highEPSS 0.3%

High (7.1) in aveva. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
This external control vulnerability, if exploited, could allow a local OS-authenticated user with standard privileges to delete files with System privilege on the machine where these products are installed, resulting in denial of service.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.3% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-610 Externally Controlled Reference to a Resource in Another Sphere
CWE-73 External Control of File Name or Path
OWASP Top 10
A05:2025 Injection, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-34982 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-34982?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-34982?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-34982 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 CNA's record in the CVE List.

ProductAffected
AVEVA SystemPlatformthrough 2020 R2 SP1 P01
AVEVA Historianthrough 2020 R2 SP1 P01
AVEVA Application Serverthrough 2020 R2 SP1 P01
AVEVA InTouchthrough 2020 R2 SP1 P01
AVEVA Enterprise Licensing (formerly known as License Manager)through 3.7.002
AVEVA Manufacturing Execution System (formerly known as Wonderware MES)through 2020 P01
AVEVA Recipe Managementthrough 2020 R2 Update 1 Patch 2
AVEVA Batch Managementthrough 2020 SP1
AVEVA Edge (formerly known as Indusoft Web Studio)through 2020 R2 SP1 P01
AVEVA Worktasks (formerly known as Workflow Management)through 2020 U2
AVEVA Plant SCADA (formerly known as Citect)through 2020 R2 Update 15
AVEVA Mobile Operator (formerly known as IntelaTrac Mobile Operator Rounds)through 2020 R1
AVEVA Communication Drivers Packthrough 2020 R2 SP1
AVEVA Telemetry Serverthrough 2020 R2 SP1

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-23-318-01AVEVA Operations Control Logger2023-11-14Critical ManufacturingAVEVA SystemPlatform: <=2020_R2_SP1_P01, AVEVA Historian: <=2020_R2_SP1_P01, AVEVA Application Server: <=2020_R2_SP1_P01 and 11 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-72 URL Encoding 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-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

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

References

Check your stackJSON