dbcve.org
Ssh CompanywebsiteApplication · Ssh Companywebsite Project

CVE-2018-14441

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-20
Fix available
A fix is available. Upgrade to after 2018-05-03 or later.
See remediation →
100/100
Remediation priority · Urgent
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 cckevincyh SSH CompanyWebsite through 2018-05-03. admin/admin/fileUploadAction_fileUpload.action allows arbitrary file upload, as demonstrated by a .jsp file with the image/jpeg content type.

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

The SSH CompanyWebsite application contains an arbitrary file upload vulnerability in the admin/admin/fileUploadAction_fileUpload.action endpoint. The application accepts file uploads without proper validation, allowing attackers to upload malicious .jsp files by spoofing the content type to image/jpeg. Since .jsp files are executable on the server, this enables remote code execution.

MitigationImplement strict file validation including both extension whitelist and magic byte verification, store uploads outside the webroot, disable script execution in upload directories, and ensure the upload endpoint requires proper authentication and authorization.

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
Ssh CompanywebsiteApplication
Affected:<= 2018-05-03

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

Work through these to decide whether this CVE applies to you.

  1. Identify the installed application
    Locate and verify the application name in your deployment. Check web application server logs, deployment descriptors, or application banner for 'Ssh Companywebsite' or 'Companywebsite' branding.
    Affected if The application is not the Ssh Companywebsite product, then this CVE does not apply.
  2. Determine the application version
    Check the deployed build artifacts, WAR file metadata, or application configuration files for the version or build date. Compare against the affected range: versions or builds dated 2018-05-03 or earlier.
    Affected if The installed version or build date is on or before 2018-05-03, placing it within the affected range.
  3. Verify the vulnerable endpoint exists
    Check if the endpoint admin/admin/fileUploadAction_fileUpload.action is present in the deployed application by inspecting the deployed WAR file or accessing the URL path directly.
    Affected if The endpoint is not present or returns a 404, the specific vulnerability path does not exist in your deployment.
  4. Inspect upload configuration and authentication
    Review the application's web.xml or security configuration to determine if the fileUploadAction_fileUpload.action endpoint is protected by authentication and if file type validation is enforced.
    Affected if The endpoint is publicly accessible without authentication OR accepts files without proper extension and content-type validation.
  5. Check upload directory script execution status
    Inspect the web server configuration (such as Tomcat's web.xml or equivalent) and the location where uploaded files are stored to determine if .jsp files in upload directories can be executed as server-side scripts.
    Affected if Uploaded .jsp files can be accessed and executed by the server, enabling remote code execution.

Your environment is affected if you are running Ssh Companywebsite version 2018-05-03 or earlier, the admin/admin/fileUploadAction_fileUpload.action endpoint is accessible, and the application does not validate file types before allowing .jsp file uploads.

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 2018-05-03
Interim mitigation

Implement strict file validation including both extension whitelist and magic byte verification, store uploads outside the webroot, disable script execution in upload directories, and ensure the upload endpoint requires proper authentication and authorization.

Fix this in Ssh Companywebsite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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