NVIDIA privilege escalation flaw disclosed

Powered by SC Magazine
 

Red Hat engineer says vendor ignored bug report.

An alleged security vulnerability has been discovered in the NVIDIA binary that leads to privilege escalation.

The flaw was posted to a Full Disclosure mailing list by Brisbane-based Red Hat software engineer Dave Airlie.

It was first discovered by an anonymous researcher and handed to Airlie for reporting to NVIDIA.

Airlie said he reported the flaw to the graphics company in June and had posted it to the public mailing list after receiving no response from the vendor.

“I was given this anonymously, it has been sent to NVIDIA over a month ago with no reply or advisory,” Airlie wrote.

He said the flaw reported by ZDNet US allows attackers to write to memory.

“It basically abuses the fact that the /dev/nvidia0 device accept(s) changes to the VGA window and moves the window around until it can read/write to somewhere useful in physical RAM," he said.

It then achieves privilege escalation by writing directly to kernel memory, he said.

Users can follow a workaround mitigation process to secure the flaw.

NVIDIA has been contacted for comment.

Copyright © SC Magazine, Australia


NVIDIA privilege escalation flaw disclosed
 
 
 
Top Stories
Earning the right to innovate
Breaking down the barriers to innovation is a long, but rewarding process, says Bank of Queensland Group CIO, Julie Bale.
 
A call for timely reporting
[Blog post] Businesses need incentives to keep customer data secure.
 
Doubts cast on Queensland's ICT Dashboard
Opposition, former Govt CIO say it can't be trusted.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  26%
 
Application integration concerns
  3%
 
Security and compliance concerns
  29%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  23%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  5%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 830

Vote