CVE-2017-14238: SQL Injection

Q: What is the severity of CVE-2017-14238?

CVE-2017-14238 is considered a high severity vulnerability due to its potential to allow remote attackers to execute arbitrary SQL commands.

Q: How do I fix CVE-2017-14238?

To fix CVE-2017-14238, upgrade to Dolibarr version 6.0.1 or later, which addresses the SQL injection vulnerability.

Q: What are the potential impacts of CVE-2017-14238?

The potential impacts of CVE-2017-14238 include unauthorized access to the database, data corruption, and exposure of sensitive information due to SQL injection.

Q: Which versions of Dolibarr are affected by CVE-2017-14238?

CVE-2017-14238 affects Dolibarr ERP/CRM version 6.0.0.

Q: Is there a workaround for CVE-2017-14238?

There are no official workarounds for CVE-2017-14238, and it is recommended to apply the software update to mitigate the risk.

Published Sep 11, 2017

Updated

SQL injection vulnerability in admin/menus/edit.php in Dolibarr ERP/CRM version 6.0.0 allows remote attackers to execute arbitrary SQL commands via the menuId parameter.

Affected Software

2 affected componentsFixes available

composer/dolibarr/dolibarr<6.0.1

6.0.1

dolibarr Dolibarr=6.0.0

Remediation

Patch Available

https://github.com/Dolibarr/dolibarr/commit/d26b2a694de30f95e46ea54ea72cc54f0d38e548

Event History

Sep 11, 2017

CVE Published

via MITRE·09:00 AM

Data Sourced

via MITRE·09:00 AM

Description

May 17, 2022

Advisory Published

via GitHub·01:05 AM

Frequently Asked Questions

What is the severity of CVE-2017-14238?

CVE-2017-14238 is considered a high severity vulnerability due to its potential to allow remote attackers to execute arbitrary SQL commands.

How do I fix CVE-2017-14238?

To fix CVE-2017-14238, upgrade to Dolibarr version 6.0.1 or later, which addresses the SQL injection vulnerability.

What are the potential impacts of CVE-2017-14238?