CVE-2018-14440
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 · uneditedAn issue was discovered in cckevincyh SSH CompanyWebsite through 2018-05-03. SQL injection exists via the admin/noticeManageAction_queryNotice.action noticeInfo parameter.
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 confidenceA SQL injection vulnerability exists in the admin/noticeManageAction_queryNotice.action endpoint of the cckevincyh SSH CompanyWebsite application. The noticeInfo parameter is not properly sanitized before being used in database queries, allowing attackers to inject malicious SQL statements.
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<= 2018-05-03CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the SSH CompanyWebsite application is deployedSearch for application files or web archives containing 'cckevincyh' or 'CompanyWebsite' branding. Check web server document roots for Java web application structures (WAR files, JSP files) associated with this project.Affected if The application codebase from cckevincyh is present in the environment.
-
Determine the application versionLocate version metadata such as build files, manifest files, or version configuration files within the deployed application. Cross-reference the build date against the cutoff of 2018-05-03.Affected if The application version is dated on or before May 3, 2018.
-
Verify the vulnerable endpoint existsCheck for the presence of the Struts/action configuration files (struts.xml, struts-config.xml) or examine the deployed WAR structure for the path admin/noticeManageAction_queryNotice.action.Affected if The admin/noticeManageAction_queryNotice.action endpoint is registered and accessible in the application routing configuration.
-
Identify noticeInfo parameter handlingExamine the NoticeManageAction or equivalent Java class handling the queryNotice action. Search for code that processes the noticeInfo request parameter without parameterized queries.Affected if The noticeInfo parameter is processed in SQL queries without prepared statements or input sanitization.
If the SSH CompanyWebsite application is deployed with a version or build date on or before 2018-05-03 and processes the noticeInfo parameter through the queryNotice action endpoint without SQL parameterization, the environment is vulnerable to CVE-2018-14440.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the noticeInfo parameter and all user-supplied inputs. Conduct a comprehensive code review to identify and remediate similar SQL injection vulnerabilities throughout the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14440 — 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-14440 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