What is the severity of CVE-2017-18392?

CVE-2017-18392 is considered a high severity vulnerability due to the possibility of data collisions in PostgreSQL databases.

How do I fix CVE-2017-18392?

To fix CVE-2017-18392, upgrade cPanel to version 68.0.15 or later.

What versions of cPanel are affected by CVE-2017-18392?

CVE-2017-18392 affects cPanel versions prior to 68.0.15, specifically versions between 63.9999.74 and 64.0.42, 65.9999.38 and 66.0.34, and 67.9999.64 and 68.0.15.

What is the impact of CVE-2017-18392?

The impact of CVE-2017-18392 is that multiple cPanel accounts can access the same PostgreSQL database, leading to potential data exposure and integrity issues.

Is there any workaround for CVE-2017-18392?

There are no documented workarounds for CVE-2017-18392; the only solution is to update to a secure version.

Vulnerability/
CVE-2017-18392

low

2.1

CWE

2/8/2019

5/8/2024

CVE-2017-18392: Input Validation

First published: Fri Aug 02 2019(Updated: )

cPanel before 68.0.15 allows collisions because PostgreSQL databases can be assigned to multiple accounts (SEC-325).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Cpanel Cpanel	>=63.9999.74<64.0.42
Cpanel Cpanel	>=65.9999.38<66.0.34
Cpanel Cpanel	>=67.9999.64<68.0.15

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-18392?
CVE-2017-18392 is considered a high severity vulnerability due to the possibility of data collisions in PostgreSQL databases.
How do I fix CVE-2017-18392?
To fix CVE-2017-18392, upgrade cPanel to version 68.0.15 or later.
What versions of cPanel are affected by CVE-2017-18392?
CVE-2017-18392 affects cPanel versions prior to 68.0.15, specifically versions between 63.9999.74 and 64.0.42, 65.9999.38 and 66.0.34, and 67.9999.64 and 68.0.15.
What is the impact of CVE-2017-18392?
The impact of CVE-2017-18392 is that multiple cPanel accounts can access the same PostgreSQL database, leading to potential data exposure and integrity issues.
Is there any workaround for CVE-2017-18392?
There are no documented workarounds for CVE-2017-18392; the only solution is to update to a secure version.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/last-modified-date
agent/tags
agent/weakness
agent/event
agent/first-publish-date
agent/description
agent/source
vendor/cpanel
canonical/cpanel cpanel
version/cpanel cpanel/63.9999.74
version/cpanel cpanel/65.9999.38
version/cpanel cpanel/67.9999.64

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-18392?
CVE-2017-18392 is considered a high severity vulnerability due to the possibility of data collisions in PostgreSQL databases.
How do I fix CVE-2017-18392?
To fix CVE-2017-18392, upgrade cPanel to version 68.0.15 or later.
What versions of cPanel are affected by CVE-2017-18392?
CVE-2017-18392 affects cPanel versions prior to 68.0.15, specifically versions between 63.9999.74 and 64.0.42, 65.9999.38 and 66.0.34, and 67.9999.64 and 68.0.15.
What is the impact of CVE-2017-18392?
The impact of CVE-2017-18392 is that multiple cPanel accounts can access the same PostgreSQL database, leading to potential data exposure and integrity issues.
Is there any workaround for CVE-2017-18392?
There are no documented workarounds for CVE-2017-18392; the only solution is to update to a secure version.