dbcve.org
CppcmsApplication

CVE-2018-11367

HIGH · 7.5 CVSS v3.0 Published 2018-05-22
Fix available
A fix is available. Upgrade to 1.2.1 or later.
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
An issue was discovered in CppCMS before 1.2.1. There is a denial of service in the JSON parser module.

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 confidence

A denial of service vulnerability exists in the JSON parser module of CppCMS versions prior to 1.2.1. The vulnerability can be exploited by providing specially crafted JSON input to the parser, causing the application to become unresponsive or crash.

MitigationUpgrade CppCMS to version 1.2.1 or later to resolve the denial of service vulnerability in the JSON parser module.

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
CppcmsApplication
Affected:< 1.2.1

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 CppCMS installation
    Search for CppCMS libraries or headers on the system. Common locations: /usr/lib/, /usr/local/lib/, or check via package manager (dpkg -l | grep cppcms, rpm -qa | grep cppcms)
    Affected if CppCMS is not found on the system - not affected. If found, proceed to version check.
  2. Determine installed CppCMS version
    Run: dpkg -l | grep cppcms (Debian) or rpm -q cppcms (Red Hat) or check library version files. Also check cmake config or header files (cppcms/version.h)
    Affected if Cannot determine version - further investigation required.
  3. Compare version against affected range
    If version is obtained, verify it is less than 1.2.1. For example, versions like 1.0.0, 1.1.0, 1.2.0 are all affected.
    Affected if Version is < 1.2.1 - the system is potentially affected by this CVE.
  4. Check if JSON parser module is in use
    Inspect application code or configuration for usage of cppcms::json::value or JSON parsing functionality. Check application logs for JSON-related operations.
    Affected if JSON parser module is actively used - exploitation is possible. Even if unused, the vulnerable library is present.

If CppCMS is installed and its version is less than 1.2.1, the environment is affected by CVE-2018-11367.

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 1.2.1 or later
Fixed in 1.2.1
Interim mitigation

Upgrade CppCMS to version 1.2.1 or later to resolve the denial of service vulnerability in the JSON parser module.

Fix this in Cppcms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-11367 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