Skip to main content
No exploitation reportedFix available

CVE-2022-28687

No exploitation reported by the sources we read.

  • Published2023-03-29
  • Fixed in2020.2.00.40
  • WeaknessCWE-427

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

This vulnerability allows remote attackers to execute arbitrary code on affected installations of AVEVA Edge 2020 SP2 Patch 0(4201.2111.1802.0000). User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of APP files. The process loads a library from an unsecured location. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16257.

Timeline

dates in UTC
  1. 2023-03-2919:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-28687?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-28687?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Aveva aveva edge
BranchAffectedFixed in
2020.2< 2020.2.00.402020.2.00.40

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-22-249-02 CISA1 known affected

    AVEVA Edge 2020 R2 SP1 and all prior versions

    AVEVA Edge: 2020 R2 SP1 and all prior versions

Full record on NVD

Fix

  1. Update Aveva aveva edge to 2020.2.00.40
  2. Vendor fix CISA ICSA-22-249-02 · 1 productFor AVEVA Edge 2020 R2 SP1, users should apply security fix HF 2020.2.00.40 (login required).
  3. Vendor fix CISA ICSA-22-249-02 · 1 productFor AVEVA Edge 2020 R2 and all prior versions (formerly known as InduSoft Web Studio), users should first upgrade to AVEVA Edge 2020 R2 SP1 (login required) and then apply security fix HF 2020.2.00.40
  4. Mitigation from the vendor CISA ICSA-22-249-02 · 1 productAVEVA recommends organizations evaluate the impact of these vulnerabilities based on their operational environment, architecture, and product implementation.
  5. Mitigation from the vendor CISA ICSA-22-249-02 · 1 productAccess Control Lists (ACLs) should be applied to all folders in which users save and load project files.
  6. Mitigation from the vendor CISA ICSA-22-249-02 · 1 productMaintain a trusted chain-of-custody on project files during creation, modification, distribution, and use.
  7. Mitigation from the vendor CISA ICSA-22-249-02 · 1 productTrain users to always verify the source of a project before opening or executing it.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2025-02-18
  • OpenCVESSVC decisionnone—
  • NVDCVSS 3.17.8read 2026-10-23
  • CNACVSS 3.07.8read 2026-10-23
  • CNAweakness (CWE)CWE-427read 2026-10-23
  • FIRST EPSSEPSS score1.0 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2023-03-29
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-28687?

This vulnerability allows remote attackers to execute arbitrary code on affected installations of AVEVA Edge 2020 SP2 Patch 0(4201.2111.1802.0000). User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of APP files. The process loads a library from an unsecured location. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16257.

Is CVE-2022-28687 actively exploited?

Active exploitation of CVE-2022-28687 has not been confirmed. Its EPSS score was 1.0% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-28687?

CVE-2022-28687 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month