Saturday, December 28, 2024
HomeCVE/vulnerabilityMultiple Vulnerabilities with Pre-installed Packages open Dell systems to Hack

Multiple Vulnerabilities with Pre-installed Packages open Dell systems to Hack

Published on

SIEM as a Service

Security experts from Talos discovered a couple of vulnerabilities in Dell Precision software which allow attackers to disable security mechanisms, escalate privileges and execute arbitrary code within the context of the application user.

CVE-2016-9038

This vulnerability exists with Invincea-X, Dell Protected Workspace 6.1.3-24058 and attacker can trigger this vulnerability by sending crafted data to the \Device\SandboxDriverApi device driver which is read/write Open to everyone.

A Successful exploitation ends in an arbitrary value written to kernel memory space, that can lead to local privilege escalation.

- Advertisement - SIEM as a Service

For More details on Vulnerability Report TALOS-2016-0256.

Also Read Vault 7 Leaks: CIA Malware “OutlawCountry” Controls Linux Machine

CVE-2016-8732

Due to inadequate restrictions on the driver communications channel, as well as inadequate validation, an attacker controlled application that is executed on an affected system could leverage this driver to effectively disable some of the protection mechanisms provided by the software.

This security vulnerability found in one of the driver components, ‘InvProtectDrv.sys’ with version 5.1.1-22303 and the vulnerability is fixed with version 6.3.0.

For More details on Vulnerability Report TALOS-2016-0246.

Also Read WordPress Visitor Statistics Plugin found Vulnerable to SQL Injection

CVE-2017-2802

This vulnerability exists with Dell Ppo Service, upon execution the program will load atiadlxx.dll which is not present in application default directory. Application searches for an appropriately named DLL in the directories defined by the PATH environment variable.

If it finds a DLL with the same name, it will load the DLL into poaService.exe without verifying the signature of the DLL. This can lead to the execution of arbitrary code if an attacker supplies a malicious DLL of the correct name.

Vulnerability exists with PPR Monitoring Plugin 3.5.5.0 and versions from v4.0 onwards are not vulnerable

For More details on Vulnerability Report TALOS-2016-2047.

Talos recommend's that organizations using affected versions of this solution
update to the latest version as quickly as possible to ensure that the protections
provided by this software cannot be bypassed by an attacker. Organizations need
to carefully consider the risks and benefits of software bundled with devices.

Also Read Lenovo VIBE Mobile Phones Vulnerable to Local Root Privilege Escalation

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

IBM AIX TCP/IP Vulnerability Lets Attackers Exploit to Launch Denial of Service Attack

IBM has issued a security bulletin warning of two vulnerabilities in its AIX operating...

Apache Auth-Bypass Vulnerability Lets Attackers Gain Control Over HugeGraph-Server

The Apache Software Foundation has issued a security alert regarding a critical vulnerability...

Node.js systeminformation Package Vulnerability Exposes Millions of Systems to RCE Attacks

A critical command injection vulnerability in the popular systeminformation npm package has recently been disclosed, exposing...