Unspecified impact through vulnerable third-party component
Published Jun 16, 2020 · Updated Aug 4, 2024
Use of a vulnerable third-party component in Schneider Electric Easergy T300 firmware 1.5.2 and earlier allows remote attackers to exploit it. The vendor advisory does not identify the component or disclose the incorrect operation performed on attacker-controlled input. Network access without authentication or user interaction is sufficient, but the resulting confidentiality, integrity, and availability consequences remain unspecified.
Summary
What happened
Use of a vulnerable third-party component in Schneider Electric Easergy T300 firmware 1.5.2 and earlier allows remote attackers to exploit it. The vendor advisory does not identify the component or disclose the incorrect operation performed on attacker-controlled input. Network access without authentication or user interaction is sufficient, but the resulting confidentiality, integrity, and availability consequences remain unspecified.
The record
- CVE
- CVE-2020-7512
- Published
- Jun 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Schneider Electric
- Product
- Easergy T300
- Classifications
- CWE-1103
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Easergy T300 (Firmware version 1.5.2 and older)
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo