What is the severity of CVE-2017-10803?

CVE-2017-10803 is considered to be of high severity due to the potential for remote code execution.

How do I fix CVE-2017-10803?

To fix CVE-2017-10803, it is recommended to upgrade Odoo to a version that does not use unpickle in the Database Anonymization module.

Who is affected by CVE-2017-10803?

CVE-2017-10803 affects users of Odoo versions 8.0, 9.0, and 10.0, both Community and Enterprise Editions.

Can CVE-2017-10803 be exploited without authentication?

No, exploitation of CVE-2017-10803 requires remote authenticated privileged user access.

What are the potential consequences of CVE-2017-10803?

The potential consequences of CVE-2017-10803 include arbitrary code execution, which can compromise the security of the system.

Vulnerability/
CVE-2017-10803

high

8.5

CWE

502

4/7/2017

5/8/2024

CVE-2017-10803

First published: Tue Jul 04 2017(Updated: )

In Odoo 8.0, Odoo Community Edition 9.0 and 10.0, and Odoo Enterprise Edition 9.0 and 10.0, insecure handling of anonymization data in the Database Anonymization module allows remote authenticated privileged users to execute arbitrary Python code, because unpickle is used.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Odoo Odoo	=8.0
Odoo Odoo	=9.0
Odoo Odoo	=9.0
Odoo Odoo	=10.0
Odoo Odoo	=10.0

Remedy

https://github.com/odoo/odoo/issues/17898

Never miss a vulnerability like this again

Reference Links

https://github.com/odoo/odoo/issues/17898

Frequently Asked Questions

What is the severity of CVE-2017-10803?
CVE-2017-10803 is considered to be of high severity due to the potential for remote code execution.
How do I fix CVE-2017-10803?
To fix CVE-2017-10803, it is recommended to upgrade Odoo to a version that does not use unpickle in the Database Anonymization module.
Who is affected by CVE-2017-10803?
CVE-2017-10803 affects users of Odoo versions 8.0, 9.0, and 10.0, both Community and Enterprise Editions.
Can CVE-2017-10803 be exploited without authentication?
No, exploitation of CVE-2017-10803 requires remote authenticated privileged user access.
What are the potential consequences of CVE-2017-10803?
The potential consequences of CVE-2017-10803 include arbitrary code execution, which can compromise the security of the system.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/references
agent/last-modified-date
agent/author
agent/remedy
agent/tags
agent/event
agent/description
agent/first-publish-date
agent/source
vendor/odoo
canonical/odoo odoo
version/odoo odoo/8.0
version/odoo odoo/9.0
version/odoo odoo/10.0

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-10803?
CVE-2017-10803 is considered to be of high severity due to the potential for remote code execution.
How do I fix CVE-2017-10803?
To fix CVE-2017-10803, it is recommended to upgrade Odoo to a version that does not use unpickle in the Database Anonymization module.
Who is affected by CVE-2017-10803?
CVE-2017-10803 affects users of Odoo versions 8.0, 9.0, and 10.0, both Community and Enterprise Editions.
Can CVE-2017-10803 be exploited without authentication?
No, exploitation of CVE-2017-10803 requires remote authenticated privileged user access.
What are the potential consequences of CVE-2017-10803?
The potential consequences of CVE-2017-10803 include arbitrary code execution, which can compromise the security of the system.