Syncthru Web ServiceApplication · Samsung

CVE-2021-42913

HIGH · 7.5 CVSS v3.1 Published 2021-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The SyncThru Web Service on Samsung SCX-6x55X printers allows an attacker to gain access to a list of SMB users and cleartext passwords by reading the HTML source code. Authentication is not required.

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 confidence

The SyncThru Web Service on Samsung SCX-6x55X printers contains an information disclosure vulnerability where SMB user credentials including cleartext passwords are embedded directly in the HTML source code of the web interface. This is a pre-authentication flaw, allowing any remote attacker to obtain valid credentials by simply requesting the page and inspecting the HTML.

MitigationApply vendor firmware updates when available. In the interim, restrict network access to the printer's web interface, disable SMB services if not required, and segment printers from sensitive network resources.

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
Syncthru Web ServiceApplication
Affected:all versions

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Confirm SyncThru Web Service is accessible
    Attempt to reach the printer's web interface by accessing http://<printer-ip> or https://<printer-ip> in a browser. The service is running if a login page loads.
    Affected if The SyncThru Web Service login page loads successfully, indicating the service is active and exposed on the network.
  2. Navigate to the SMB configuration page
    In the web interface, locate the SMB or network sharing settings. This is typically found under Network Settings, SMB Settings, or a similar section where printer sharing is configured.
    Affected if The page loads and displays SMB configuration options, meaning SMB functionality is enabled on the device.
  3. View the page source HTML
    Right-click on the SMB configuration page and select 'View Page Source' (or use browser developer tools, Ctrl+Shift+I, and inspect the HTML).
    Affected if The page source can be viewed, indicating the HTML is accessible for inspection.
  4. Search for embedded credentials in HTML
    In the page source, search for patterns such as 'password', 'pwd', 'credential', or look for visible or hidden form fields containing password values. Specifically look for input fields or JavaScript variables that contain SMB username and password values.
    Affected if Cleartext SMB credentials (usernames and/or passwords) appear anywhere in the HTML source code, indicating the vulnerability is present.

A user is affected if the SyncThru Web Service is accessible and the HTML source of any page (particularly SMB configuration pages) contains cleartext SMB credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. In the interim, restrict network access to the printer's web interface, disable SMB services if not required, and segment printers from sensitive network resources.

Fix this in Syncthru Web Service Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-42913 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