CVE-2024-37993
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 SIMATIC Reader RF610R CMIIT (6GT2811-6BC10-2AA0) (All versions < V4.2), SIMATIC Reader RF610R ETSI (6GT2811-6BC10-0AA0) (All versions < V4.2), SIMATIC Reader RF610R FCC (6GT2811-6BC10-1AA0) (All versions < V4.2), SIMATIC Reader RF615R CMIIT (6GT2811-6CC10-2AA0) (All versions < V4.2), SIMATIC Reader RF615R ETSI (6GT2811-6CC10-0AA0) (All versions < V4.2), SIMATIC Reader RF615R FCC (6GT2811-6CC10-1AA0) (All versions < V4.2), SIMATIC Reader RF650R ARIB (6GT2811-6AB20-4AA0) (All versions < V4.2), SIMATIC Reader RF650R CMIIT (6GT2811-6AB20-2AA0) (All versions < V4.2), SIMATIC Reader RF650R ETSI (6GT2811-6AB20-0AA0) (All versions < V4.2), SIMATIC Reader RF650R FCC (6GT2811-6AB20-1AA0) (All versions < V4.2), SIMATIC Reader RF680R ARIB (6GT2811-6AA10-4AA0) (All versions < V4.2), SIMATIC Reader RF680R CMIIT (6GT2811-6AA10-2AA0) (All versions < V4.2), SIMATIC Reader RF680R ETSI (6GT2811-6AA10-0AA0) (All versions < V4.2), SIMATIC Reader RF680R FCC (6GT2811-6AA10-1AA0) (All versions < V4.2), SIMATIC Reader RF685R ARIB (6GT2811-6CA10-4AA0) (All versions < V4.2), SIMATIC Reader RF685R CMIIT (6GT2811-6CA10-2AA0) (All versions < V4.2), SIMATIC Reader RF685R ETSI (6GT2811-6CA10-0AA0) (All versions < V4.2), SIMATIC Reader RF685R FCC (6GT2811-6CA10-1AA0) (All versions < V4.2), SIMATIC RF1140R (6GT2831-6CB00) (All versions < V1.1), SIMATIC RF1170R (6GT2831-6BB00) (All versions < V1.1), SIMATIC RF166C (6GT2002-0EE20) (All versions < V2.2), SIMATIC RF185C (6GT2002-0JE10) (All versions < V2.2), SIMATIC RF186C (6GT2002-0JE20) (All versions < V2.2), SIMATIC RF186CI (6GT2002-0JE50) (All versions < V2.2), SIMATIC RF188C (6GT2002-0JE40) (All versions < V2.2), SIMATIC RF188CI (6GT2002-0JE60) (All versions < V2.2), SIMATIC RF360R (6GT2801-5BA30) (All versions < V2.2). The affected applications do not authenticated the creation of Ajax2App instances. This could allow an unauthenticated attacker to cause a denial of service condition.
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 · moderate confidenceMultiple SIMATIC Reader RF devices and SIMATIC RF controllers contain an authentication bypass vulnerability where the applications fail to validate authentication when creating Ajax2App instances. An unauthenticated remote attacker can exploit this by directly creating these instances, causing the affected devices to become unavailable (denial of service).
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< 2.2< 1.1< 1.1< 4.2< 4.2< 4.2< 4.2< 4.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify the SIMATIC RF device modelAccess the device web interface, check the device nameplate, or use the device's management interface to determine the exact model (e.g., RF360R, RF1170R, RF1140R, RF685R, RF680R)Affected if Device is not one of the listed affected models (RF360R, RF1170R, RF1140R, RF685R variants, RF680R)
-
Determine the installed firmware versionAccess the device web interface or management console and navigate to the firmware/version information section to retrieve the current firmware version numberAffected if Unable to retrieve firmware version for comparison
-
Compare firmware version for RF360RIf device is RF360R, check if firmware version is less than 2.2Affected if Firmware version < 2.2
-
Compare firmware version for RF1170R and RF1140RIf device is RF1170R or RF1140R, check if firmware version is less than 1.1Affected if Firmware version < 1.1
-
Compare firmware version for RF685R and RF680R variantsIf device is RF685R (any variant: FCC, ETSI, CMIIT, ARIB) or RF680R FCC, check if firmware version is less than 4.2Affected if Firmware version < 4.2
The environment is affected if a SIMATIC RF device (RF360R, RF1170R, RF1140R, RF685R, or RF680R) is running firmware version below the corresponding threshold (2.2, 1.1, or 4.2 depending on model).
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.
dbcve · scoped1.12.24.2
Apply vendor-supplied firmware updates: upgrade SIMATIC Reader RF6x0R/RF6x5R/RF680R/RF685R to version V4.2 or higher; upgrade RF1140R and RF1170R to version V1.1 or higher; upgrade RF166C, RF185C, RF186C, RF186CI, RF188C, RF188CI, and RF360R to version V2.2 or higher.
RF360R: V2.2 | RF1170R: V1.1 | RF1140R: V1.1 | RF685R/RF680R/RF650R/RF615R/RF610R: V4.2 | RF166C/RF185C/RF186C/RF186CI/RF188C/RF188CI: V2.2
- 1. Identify the exact model number of the affected SIMATIC device from the list (e.g., RF360R, RF1170R, RF1140R, RF685R FCC/ETSI/CMIIT/ARIB, RF680R FCC, etc.)
- 2. Access the device management interface or use Siemens' industrial software tools (e.g., Totally Integrated Automation Portal) to check the current firmware version
- 3. Download the corresponding firmware update from Siemens' official support portal (cert-portal.siemens.com) or the Siemens Product Support website
- 4. Follow the manufacturer's firmware update procedure, typically involving uploading the firmware file through the device's web interface or management software
- 5. After flashing the firmware, verify the device is running the fixed version (RF360R: V2.2, RF1170R: V1.1, RF1140R: V1.1, RF685R/RF680R/RF650R/RF615R/RF610R: V4.2, RF166C/RF185C/RF186C/RF186CI/RF188C/RF188CI: V2.2)
- 6. Test that the Ajax2App creation now requires proper authentication and the device no longer enters a denial of service condition from unauthenticated requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37993 — 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-2024-37993 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