dbcve.org
EdgeWeb browser · Aveva

CVE-2021-42794

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-16
Fix available
A fix is available. Upgrade to 2020 or later.
See remediation →
62/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in AVEVA Edge (formerly InduSoft Web Studio) versions R2020 and prior. The application allows a client to provide a malicious connection string that could allow an adversary to port scan the LAN, depending on the hosts' responses.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EdgeWeb browser
Affected:< 2020= 2020

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2020 or later
Fixed in 2020
Recommended fix Moderate confidence

AVEVA Edge R2020 Update 1 or later (R2021/R2022)

  1. Check the current installed version of AVEVA Edge (InduSoft Web Studio) by opening the application and navigating to Help > About, or by checking the installed programs list in Windows Control Panel.
  2. Identify the specific build version - the vulnerability affects versions R2020 and prior including R2020.
  3. Contact AVEVA customer support or visit the official AVEVA support portal to obtain the latest patched version for AVEVA Edge.
  4. AVEVA typically releases updates as service packs or hotfixes - request information on the R2020 update that addresses security vulnerabilities.
  5. Alternatively, download the most recent AVEVA Edge version from the official AVEVA website (www.aveva.com) under the downloads or support section.
  6. Before upgrading, backup all project files, applications, and configurations.
  7. Install the updated version following the standard AVEVA installation procedures.
  8. Verify the installation was successful and test critical functionality.
Caveat Minor compatibility issues possible with older project files; review release notes for breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-42794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-42794 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data