Remote Service ManagerApplication · Cybozu

CVE-2018-16172

MEDIUM · 6.5 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 3.1.8 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Improper countermeasure against clickjacking attack in client certificates management screen was discovered in Cybozu Remote Service 3.0.0 to 3.1.8, that allows remote attackers to trick a user to delete the registered client certificate.

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

A clickjacking vulnerability exists in Cybozu Remote Service versions 3.0.0 through 3.1.8 within the client certificates management screen. Attackers can embed the application's interface in an invisible frame and trick authenticated users into clicking on hidden elements, specifically to delete registered client certificates. This improper countermeasure allows remote attackers to manipulate user actions through overlaid malicious interfaces.

MitigationImplement X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN headers, and/or configure Content Security Policy (CSP) frame-ancestors directive to prevent the application from being embedded in iframes.

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.0.0, <= 3.1.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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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. Check installed Cybozu Remote Service Manager version
    Locate the installed version of Cybozu Remote Service Manager in the system information or about page, typically accessible via the administration console or product documentation
    Affected if The installed version falls within 3.0.0 through 3.1.8 (inclusive)
  2. Verify access to client certificates management screen
    Log in as an authenticated user and navigate to the client certificates management interface within the application
    Affected if The client certificates management functionality is accessible and enabled for the user
  3. Test for iframe embedding vulnerability
    Attempt to embed the application URL in an HTML iframe element from an external domain, or inspect HTTP response headers for X-Frame-Options and Content-Security-Policy frame-ancestors directives
    Affected if The application can be embedded in a frame (no X-Frame-Options: DENY/SAMEORIGIN and no CSP frame-ancestors restricting embed)
  4. Confirm authenticated session exposure
    Verify that the application allows authenticated users to access sensitive functions via the web interface while the clickjacking frame can be overlaid
    Affected if The application processes actions from authenticated sessions when embedded in a third-party frame

The environment is affected if Cybozu Remote Service Manager version 3.0.0 through 3.1.8 is installed AND the application can be embedded in iframes by external sites, allowing attackers to trick authenticated users into deleting client certificates.

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
Upgrade available Upgrade to a release after 3.1.8
Interim mitigation

Implement X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN headers, and/or configure Content Security Policy (CSP) frame-ancestors directive to prevent the application from being embedded in iframes.

Fix this in Remote Service Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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