Two new security vulnerabilities have been revealed in Adobe's Version Cue software, according to security consulting firm iDefense Inc.
Adobe has issued a patch to repair the flaws.
Both allow local attackers to gain root privileges to a machine through Version Cue, the file-version manager in Adobe's Creative Suite software, according to Michael Sutton, director of iDefense Labs at iDefense.
One flaw is a "library loading vulnerability" that enables potential hackers to load a custom library by executing a method from the command line of VCNative, a root application in Version Cue, said Rich Johnson, a senior security engineer with iDefense Labs. In this way, someone could take full control of a system and gain root privileges, thus enabling them to introduce malicious code.
The other way someone could gain root privileges through Version Cue is to exploit the log file created when the root application VCNative begins running, he said. The log file is always called the same thing, and if a person "knows what it's called they could put a file in there that would allow redirection of that file to a location of choice, then can override special system files with this," Johnson said.
Adobe counsels caution
Though published reports claim the flaws affect the most recent version of the suite, Creative Suite 2, an Adobe spokesman denied this. The flaws only affect the previous Creative Suite release, which came out in August 2003, said Bob Schaffel, senior product manager of Version Cue for Adobe.
Sutton said the flaws are "far from the sexiest vulnerabilities we’ve ever seen" since they can only be exploited by local attackers, meaning they must have access to the machine to exploit the flaws. Also, the flaws only affect versions of Creative Suite for Mac OS X, so there is a "limited user base" that is affected, he said.
The recent spate of vulnerabilities are not indicative of a lack of overall security in Adobe's software platform, but instead are the inevitable result of developing a broad portfolio of software, Schaffel said.
"I don’t think this should be seen as some kind of internal trend," he said. "When you consider the broad number of products and the enormous amount of code [we develop], every now and then something like this manages to slip through."