Remote Service ManagerApplication · Cybozu

CVE-2021-20801

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Cybozu Remote Service 3.1.8 to 3.1.9 allows a remote authenticated attacker to conduct XML External Entity (XXE) attacks and obtain the information stored in the product via unspecified vectors. This issue occurs only when using Mozilla Firefox.

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

Cybozu Remote Service versions 3.1.8 to 3.1.9 contains an XML External Entity (XXE) vulnerability that allows authenticated remote attackers to exploit improper XML parsing and obtain sensitive information stored in the product. The attack vector is limited to Mozilla Firefox users, suggesting a browser-specific parsing behavior or configuration issue.

MitigationApply the vendor patch for CVE-2021-20801 or upgrade to a patched version. If no patch is available, disable external entity processing in the XML parser configuration and consider restricting Firefox usage until remediation is complete.

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
Remote Service ManagerApplication
Affected:= 3.1.8= 3.1.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Cybozu Remote Service version
    Access the product's system information or about page, or run the version command provided in the product documentation
    Affected if the installed version is 3.1.8 or 3.1.9
  2. Confirm version falls within affected range
    Compare your installed version against the affected range 3.1.8 to 3.1.9 inclusive
    Affected if the version is exactly 3.1.8 or exactly 3.1.9
  3. Verify XML parsing is in use
    Inspect whether the product processes XML data through user-supplied input, file uploads, or API calls that accept XML content
    Affected if XML parsing functionality is enabled and accepts external input
  4. Check authentication status
    Verify whether authentication is required for accessing the affected XML parsing feature
    Affected if the attacker can authenticate to the service (authentication is not disabled)
  5. Identify browser in use
    Determine which web browser users employ to access the Cybozu Remote Service interface
    Affected if users access the service using Mozilla Firefox (the attack vector is limited to Firefox users)

You are affected if your Cybozu Remote Service is version 3.1.8 or 3.1.9, the XML parsing feature is enabled with external input, authentication can be obtained, and users access the service via Mozilla Firefox.

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 the vendor patch for CVE-2021-20801 or upgrade to a patched version. If no patch is available, disable external entity processing in the XML parser configuration and consider restricting Firefox usage until remediation is complete.

Fix this in Remote Service Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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