dbcve.org
Ultimaker S3 FirmwareOperating system · Ultimaker

CVE-2021-34087

HIGH · 7.1 CVSS v3.1 Published 2022-01-10
Fix available
A fix is available. Upgrade to after 6.3 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
In Ultimaker S3 3D printer, Ultimaker S5 3D printer, Ultimaker 3 3D printer S-line through 6.3 and Ultimaker 3 through 5.2.16, the local webserver can be used for clickjacking. This includes the settings page.

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

The Ultimaker S3, S5, and Ultimaker 3 (both S-line and standard) 3D printers with vulnerable firmware versions lack X-Frame-Options or Content Security Policy frame-ancestors headers on their local webserver, allowing the printer settings page to be embedded in a transparent iframe. Attackers can trick authenticated users into unknowingly clicking hidden buttons to modify printer settings.

MitigationAdd X-Frame-Options: DENY or SAMEORIGIN header and/or Content-Security-Policy with frame-ancestors directive to the printer's web server configuration to prevent clickjacking attacks.

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
Ultimaker S3 FirmwareOperating system
Affected:<= 6.3
Ultimaker S5 FirmwareOperating system
Affected:<= 6.3
Ultimaker 3 FirmwareOperating system
Affected:<= 5.2.16

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 printer model and firmware version
    Access the printer's web interface (http://<printer-ip>) and navigate to Settings > About to view the firmware version. Alternatively, check the printer display under Settings > About > Printer.
    Affected if Firmware version is <= 6.3 on Ultimaker S3 or S5, or <= 5.2.16 on Ultimaker 3 (any model variant).
  2. Verify web interface is accessible
    Open a browser or use curl to request the printer's main page (http://<printer-ip>/) and confirm it loads.
    Affected if The web interface is reachable over the network (printer is networked).
  3. Check for X-Frame-Options header
    Use browser developer tools (Network tab) or run 'curl -I http://<printer-ip>/' to inspect HTTP response headers. Look for 'X-Frame-Options' in the headers.
    Affected if The X-Frame-Options header is absent from the HTTP response.
  4. Check for Content-Security-Policy frame-ancestors directive
    Inspect HTTP response headers as above. Look for 'Content-Security-Policy' header and check if it includes the 'frame-ancestors' directive.
    Affected if Content-Security-Policy header is missing OR exists but does not include the frame-ancestors directive.

A user is affected if their printer model and firmware version fall within the affected ranges AND the web interface responds without X-Frame-Options and without CSP frame-ancestors protection.

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 a release after 6.3
Interim mitigation

Add X-Frame-Options: DENY or SAMEORIGIN header and/or Content-Security-Policy with frame-ancestors directive to the printer's web server configuration to prevent clickjacking attacks.

Recommended fix Moderate confidence

Ultimaker S3/S5: firmware >6.3 (check ultimaker.com for exact latest stable release); Ultimaker 3: firmware >5.2.16

  1. 1. Navigate to the Ultimaker support website (ultimaker.com/support) or the firmware download page
  2. 2. Locate the firmware download section for your specific printer model (Ultimaker S3, S5, or 3)
  3. 3. Download the latest available firmware version that is newer than the affected versions (S3/S5: >6.3, Ultimaker 3: >5.2.16)
  4. 4. Follow the official Ultimaker firmware update instructions to install the new firmware via USB or through the printer's network interface
  5. 5. After updating, verify that the X-Frame-Options header is properly set by inspecting HTTP responses from the printer's webserver using browser developer tools or a curl command
  6. 6. Confirm that the settings page can no longer be embedded in iframes by testing that the response includes appropriate clickjacking protections
Caveat Firmware updates may reset some printer settings to defaults; verify all printer configurations after upgrade

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

Fix this in Ultimaker S3 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34087 — 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-34087 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