CVE-2018-0614
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 · uneditedCross-site scripting vulnerability in 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 attackers to inject arbitrary web script or HTML 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 · moderate confidenceCross-site scripting (XSS) vulnerability in NEC Platforms Calsos CSDX and CSDJ series web interfaces allows remote attackers to inject arbitrary JavaScript or HTML through unsanitized user input. The vulnerability affects multiple product lines and versions, with a CVSS base score of 6.1 indicating moderate severity.
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<= 1.37210411<= 4.37210411<= 2.37210411<= 3.37210411<= 01.03.00<= 01.03.00<= 01.03.00<= 03.00.00CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NEC Calsos product modelAccess the device administrative interface or check device documentation/labels to confirm the exact model (CSDX, CSDX(P), CSDX(S), CSDX(D), CSDJ-A, CSDJ-B, CSDJ-D, or CSDJ-H).Affected if The model is any of the CSDX or CSDJ series listed in affected products.
-
Check firmware versionNavigate to the web interface system information or firmware version page, typically found under Settings, System, or About sections in the Calsos administration panel.Affected if The firmware version is at or below 1.37210411 (CSDX), 4.37210411 (CSDX(P)), 2.37210411 (CSDX(S)), 3.37210411 (CSDX(D)), 01.03.00 (CSDJ-B/D/H), or 03.00.00 (CSDJ-A).
-
Verify web interface is exposedConfirm the device web management interface is accessible over HTTP/HTTPS from network locations. Check router/firewall rules and device network configuration.Affected if The web interface is accessible from network segments beyond the trusted local administration zone.
-
Test for unsanitized input reflectionSubmit a benign test script payload such as <script>alert('XSS')</script> in common input fields (login forms, search fields, parameter inputs in URLs) within the Calsos web interface.Affected if The submitted payload is reflected back and executed in the browser without proper encoding.
A defender is affected if they run any NEC Calsos CSDX or CSDJ series device with firmware versions at or below the thresholds listed, and the web interface is accessible for exploitation.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches for the specific affected versions (CSDX 1.37210411+, CSDX(P) 4.37210411+, CSDX(D) 3.37210411+, CSDX(S) 2.37210411+, CSDJ-B/H/D 01.03.01+, CSDJ-A 03.00.01+). Implement input validation and output encoding as defense-in-depth until patches are applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0614 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-0614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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