What is the severity of CVE-2019-20451?

CVE-2019-20451 is rated as a high severity vulnerability due to its potential for remote code execution.

How does CVE-2019-20451 allow remote code execution?

CVE-2019-20451 allows remote code execution by permitting the upload of a malicious file, RebootSystem.lnk, via specific API calls.

What versions are affected by CVE-2019-20451?

CVE-2019-20451 affects Samsung Prismview System 9 version 11.10.17.00 and Prismview Player 11 version 13.09.1100.

Is authentication required to exploit CVE-2019-20451?

Yes, authentication is required to exploit CVE-2019-20451, although credentials can be obtained from a downloadable XML file.

What mitigations are recommended for CVE-2019-20451?

To mitigate CVE-2019-20451, it is recommended to restrict access to the API and ensure software is updated to patched versions.

Vulnerability/
CVE-2019-20451

critical

CWE

434

10/2/2020

5/8/2024

CVE-2019-20451: Malicious File Upload

First published: Mon Feb 10 2020(Updated: )

The HTTP API in Prismview System 9 11.10.17.00 and Prismview Player 11 13.09.1100 allows remote code execution by uploading RebootSystem.lnk and requesting /REBOOTSYSTEM or /RESTARTVNC. (Authentication is required but an XML file containing credentials can be downloaded.)

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Samsung Prismview Player 11	=13.09.1100
Samsung Prismview System 9	=11.10.17.00

Never miss a vulnerability like this again

Reference Links

https://www.exploit-db.com/papers/47535

Frequently Asked Questions

What is the severity of CVE-2019-20451?
CVE-2019-20451 is rated as a high severity vulnerability due to its potential for remote code execution.
How does CVE-2019-20451 allow remote code execution?
CVE-2019-20451 allows remote code execution by permitting the upload of a malicious file, RebootSystem.lnk, via specific API calls.
What versions are affected by CVE-2019-20451?
CVE-2019-20451 affects Samsung Prismview System 9 version 11.10.17.00 and Prismview Player 11 version 13.09.1100.
Is authentication required to exploit CVE-2019-20451?
Yes, authentication is required to exploit CVE-2019-20451, although credentials can be obtained from a downloadable XML file.
What mitigations are recommended for CVE-2019-20451?
To mitigate CVE-2019-20451, it is recommended to restrict access to the API and ensure software is updated to patched versions.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/references
agent/author
agent/event
agent/description
agent/first-publish-date
agent/tags
agent/source
vendor/samsung
canonical/samsung prismview player 11
version/samsung prismview player 11/13.09.1100
canonical/samsung prismview system 9
version/samsung prismview system 9/11.10.17.00

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-2019-20451?
CVE-2019-20451 is rated as a high severity vulnerability due to its potential for remote code execution.
How does CVE-2019-20451 allow remote code execution?
CVE-2019-20451 allows remote code execution by permitting the upload of a malicious file, RebootSystem.lnk, via specific API calls.
What versions are affected by CVE-2019-20451?
CVE-2019-20451 affects Samsung Prismview System 9 version 11.10.17.00 and Prismview Player 11 version 13.09.1100.
Is authentication required to exploit CVE-2019-20451?
Yes, authentication is required to exploit CVE-2019-20451, although credentials can be obtained from a downloadable XML file.
What mitigations are recommended for CVE-2019-20451?
To mitigate CVE-2019-20451, it is recommended to restrict access to the API and ensure software is updated to patched versions.