CVE-2019-10924
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 · uneditedA vulnerability has been identified in LOGO! Soft Comfort (All versions < V8.3). The vulnerability could allow an attacker to execute arbitrary code if the attacker tricks a legitimate user to open a manipulated project. In order to exploit the vulnerability, a valid user must open a manipulated project file. No further privileges are required on the target system. The vulnerability could compromise the confidentiality, integrity and availability of the engineering station. At the time of advisory publication no public exploitation of this security vulnerability was known.
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 · high confidenceA code execution vulnerability exists in LOGO! Soft Comfort versions prior to V8.3. The flaw is triggered when a user opens a specially crafted manipulated project file, likely due to insufficient input validation during project file parsing. This allows an attacker to execute arbitrary code on the victim's engineering station with the same privileges as the legitimate user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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< 8.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if LOGO! Soft Comfort is installedLook for the software in standard installation directories such as C:\Program Files\Siemens\LOGO! Soft Comfort or check Windows Programs and Features (Add/Remove Programs) for an entry named 'LOGO! Soft Comfort'Affected if LOGO! Soft Comfort appears in installed programs
-
Determine the installed versionRight-click on the LOGO! Soft Comfort executable (typically named LogoSoftComfort.exe) in the installation folder, select Properties, then go to the Details tab to view the File VersionAffected if The displayed File Version is lower than 8.3.0 or the product version shows a number less than 8.3
-
Check program version through installed programs listIn Windows Control Panel > Programs and Features, locate 'LOGO! Soft Comfort' and check the Version column in the program entryAffected if The version shown is blank or shows a version number less than 8.3
-
Identify associated project file typesCheck for .lsc or .logo file extensions on the system, which are the project file formats used by LOGO! Soft Comfort. These files are typically stored in user documents or project foldersAffected if Project files with .lsc or .logo extensions exist and the software version is confirmed as less than 8.3
The environment is affected if LOGO! Soft Comfort is installed with any version prior to 8.3, as opening a specially crafted .lsc or .logo project file could allow arbitrary code execution.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data8.3
Upgrade LOGO! Soft Comfort to version 8.3 or later. Until upgraded, exercise extreme caution with project files from untrusted sources and implement additional endpoint protection controls.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10924 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10924 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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