CVE-2019-6823
No exploitation reported by the sources we read.
- Published2019-07-15
- Fixed in8.0.0
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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
A CWE-94: Code Injection vulnerability exists in ProClima (all versions prior to version 8.0.0) which could allow an unauthenticated, remote attacker to execute arbitrary code on the targeted system in all versions of ProClima prior to version 8.0.0.
Timeline
dates in UTC- 2019-07-1521:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-6823?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-6823?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | < 8.0.0 | 8.0.0 | NVD |
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-19-295-01_Schneider Electric ProClima
ProClima: all versions prior to 8.0.0
Fix
- Update Schneider-electric proclima to 8.0.0
- Vendor fix CISA ICSA-19-295-01 · 1 productSchneider Electric has released Version 8.0.0 of ProClima and recommends users upgrade to this version or newer.
- Mitigation from the vendor CISA ICSA-19-295-01 · 1 productFor more information on these vulnerabilities and the associated upgrade, please see Schneider Electric's SEVD-2019-162-01
- Mitigation from the vendor CISA ICSA-19-295-01 · 1 productLocate control and safety system networks and remote devices behind firewalls and isolate them from the business network.
- Mitigation from the vendor CISA ICSA-19-295-01 · 1 productPhysical controls should be in place so no unauthorized person has access to the ICS and safety controllers, peripheral equipment, or the ICS and safety networks.
- Mitigation from the vendor CISA ICSA-19-295-01 · 1 productAll controllers should reside in locked cabinets and never be left in “Program” mode.
- Mitigation from the vendor CISA ICSA-19-295-01 · 1 productAll programming software should be kept in locked cabinets and should never be connected to any network other than the network for devices intended.
Advisories and patches
- www.schneider-electric.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- CNAweakness (CWE)CWE-94read 2026-10-23
- NVDweakness (CWE)CWE-94read 2026-10-23
- FIRST EPSSEPSS score5.0 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-07-15
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-6823?
Is CVE-2019-6823 actively exploited?
What is the CVSS score for CVE-2019-6823?
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
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.