Calsos Csdx FirmwareOperating system · Necplatforms

CVE-2018-0613

HIGH · 8.8 CVSS v3.0 Published 2018-07-26
Fix available
A fix is available. Upgrade to after 4.37210411 or later.
See remediation →
94/100
Remediation priority · Urgent
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
NEC Platforms Calsos CSDX and CSDJ series products (CSDX 1.37210411 and earlier, CSDX(P) 4.37210411 and earlier, CSDX(D) 3.37210411 and earlier, CSDX(S) 2.37210411 and earlier, CSDJ-B 01.03.00 and earlier, CSDJ-H 01.03.00 and earlier, CSDJ-D 01.03.00 and earlier, CSDJ-A 03.00.00) allows remote authenticated attackers to bypass access restriction to conduct arbitrary operations with administrative privilege via unspecified vectors.

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

Authentication bypass vulnerability in NEC Calsos CSDX and CSDJ series products allows remote authenticated attackers to escalate privileges to administrative level, bypassing access restrictions through unspecified vectors.

MitigationApply vendor-provided firmware/software updates to all affected CSDX and CSDJ product versions. Until patched, restrict network access to these systems to trusted users only and monitor for unauthorized administrative activity.

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
Calsos Csdx FirmwareOperating system
Affected:<= 1.37210411
Calsos Csdx\(p\) FirmwareOperating system
Affected:<= 4.37210411
Calsos Csdx\(s\) FirmwareOperating system
Affected:<= 2.37210411
Calsos Csdx\(d\) FirmwareOperating system
Affected:<= 3.37210411
Calsos Csdj B FirmwareOperating system
Affected:<= 01.03.00
Calsos Csdj D FirmwareOperating system
Affected:<= 01.03.00
Calsos Csdj H FirmwareOperating system
Affected:<= 01.03.00
Calsos Csdj A FirmwareOperating system
Affected:<= 03.00.00

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

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

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 if the system is a NEC Calsos CSDX or CSDJ device
    Check the device model number, system information page, or product documentation to confirm the product is one of the following series: CSDX, CSDX(p), CSDX(s), CSDX(d), CSDJ B, CSDJ D, CSDJ H, or CSDJ A
    Affected if The device is any of the listed NEC Calsos CSDX or CSDJ series models
  2. Determine the installed firmware version
    Access the device administrative interface or use the vendor-provided management tool to view the firmware version information. This is typically found in System Settings, About, or Device Information pages
    Affected if The firmware version cannot be verified or is at or below the affected version numbers for your specific model
  3. Compare your firmware version against affected ranges
    Match your exact model variant to its version threshold: CSDX <= 1.37210411, CSDX(p) <= 4.37210411, CSDX(s) <= 2.37210411, CSDX(d) <= 3.37210411, CSDJ B/D/H <= 01.03.00, CSDJ A <= 03.00.00
    Affected if Your firmware version is equal to or lower than the threshold for your specific model variant
  4. Verify the device is network accessible with valid credentials
    Confirm that remote authentication is enabled and the management interface is accessible over the network. Check if web-based or API-based remote administration is active
    Affected if Remote authentication is enabled and the device is accessible over the network, which allows the authentication bypass vector to be exploited

You are affected if your device is a NEC Calsos CSDX or CSDJ series model with firmware version at or below the threshold for your specific variant, and remote authentication is enabled.

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 4.37210411
Interim mitigation

Apply vendor-provided firmware/software updates to all affected CSDX and CSDJ product versions. Until patched, restrict network access to these systems to trusted users only and monitor for unauthorized administrative activity.

Fix this in Calsos Csdx Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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