dbcve.org
Ftmg FirmwareOperating system · Sick

CVE-2021-32504

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to 2.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unauthenticated users can access sensitive web URLs through GET request, which should be restricted to maintenance users only. A malicious attacker could use this sensitive information’s to launch further attacks on the system.

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 confidence

This is an authentication bypass vulnerability where unauthenticated users can access sensitive web URLs intended only for maintenance users via GET requests. The issue allows unauthorized access to maintenance-related endpoints that should require proper authentication, potentially exposing sensitive system information.

MitigationImplement proper access control checks on all maintenance URLs to ensure only authenticated and authorized maintenance users can access sensitive endpoints. All sensitive web URLs should require authentication and role-based authorization before granting access.

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
Ftmg FirmwareOperating system
Affected:< 2.8

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Sick Ftmg device in your environment
    Locate any SICK FTMG hardware or software installations in your network inventory or physically in your facility
    Affected if The device/product is a Sick Ftmg system
  2. Determine the installed firmware version
    Access the device management interface or system settings to view the current firmware version; consult product documentation for version lookup commands if needed
    Affected if The firmware version is less than 2.8 (e.g., 2.7, 2.6, earlier versions)
  3. Identify maintenance-related web endpoints
    Review the application's URL structure or API documentation to locate maintenance-related paths (commonly /maintenance, /admin, /debug, or similar administrative endpoints)
    Affected if The product exposes web-based maintenance or administrative endpoints
  4. Test unauthenticated access to maintenance URLs
    Send a GET request to suspected maintenance endpoints without providing any authentication credentials or session tokens
    Affected if The request returns a successful response (HTTP 200) instead of requiring authentication (e.g., redirect to login, HTTP 401/403)

You are affected if you have a Sick Ftmg device running firmware version less than 2.8 and maintenance web URLs are accessible without any authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.8 or later
Fixed in 2.8
Interim mitigation

Implement proper access control checks on all maintenance URLs to ensure only authenticated and authorized maintenance users can access sensitive endpoints. All sensitive web URLs should require authentication and role-based authorization before granting access.

Recommended fix Moderate confidence

Firmware version 2.8 or later

  1. Identify all SICK Ftmg devices on the network running firmware versions prior to 2.8
  2. Access the device management interface and verify the current firmware version
  3. Obtain the official firmware version 2.8 or later from SICK's official support portal (sick.com)
  4. Follow SICK's documented firmware upgrade procedure to apply version 2.8 or later
  5. After upgrading, verify the device is functioning correctly
  6. Confirm that unauthenticated users can no longer access sensitive web URLs that should require maintenance user authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ftmg Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32504 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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