LWN.net Logo

Security

Oxford blocks Google Docs as a phishing countermeasure

By Nathan Willis
March 7, 2013

Google services are nearly ubiquitous these days. Although the most oft-repeated concern is that this ubiquity compromises user privacy, recent action by Oxford University illustrates that there are other risks accompanying the search giant's omnipresence, such as security. Robin Stevens, from the University's IT department, posted a blog entry about the action on February 18, explaining that IT "recently felt it necessary to take, temporarily, extreme action for the majority of University users: we blocked Google Docs." University officials enforced the block for only two and a half hours, not to combat the security threat itself, but to get the attention of its own users.

Go phish

The issue at hand is phishing attacks delivered via Google Docs's web forms. Phishing itself is not a new problem, Stevens noted, but historically phishing attacks would be delivered as email messages asking the recipient to reply and include account information (such as the password). The replying accounts would then be taken over and used as a platform from which to send out thousands of spam emails through the university's email servers. As a large, established university, Oxford's servers are implicitly trusted by many other email providers and ISPs, which raises the chance of the outgoing spam flood sneaking past filters. This type of email-based phishing attack would generally masquerade as an urgent request from some on-campus office (such as IT itself), warning the user of a policy violation, a full mailbox, or some other issue requiring rapid attention.

These days, however, direct-reply phishing is on the decline, and the more common approach is to trick users into visiting a legitimate-looking web form. Like the phishing email, this form masquerades as official communication, perhaps asking the user to log in (with his or her real password) to take care of some urgent account problem. The trouble is that Google Docs offers a free web form creation service—and it delivers it over SSL, thus making it harder for the university's anti-malware defenses to detect. Stevens reported that recent weeks had seen a "marked increase" in such phishing activity, and that although the majority of the university's users spotted the scams, a small proportion did not.

Now, we may be home to some of the brightest minds in the nation. Unfortunately, their expertise in their chosen academic field does not necessarily make them an expert in dealing with such mundane matters as emails purporting to be from their IT department. Some users simply see that there's some problem, some action is required, carry it out, and go back to considering important matters such as the mass of the Higgs Boson, or the importance of the March Hare to the Aztecs.

With even a small fraction of the tens of thousands of university email users falling for the phishing forms, a sizable number of accounts were compromised—and, presumably, could be used to mount spam floods at any time. That put the university at additional risk, Stevens said, because in the past there have been incidents where major email providers began rejecting Oxford email due to large-scale spam. The recent surge in Google Docs form-phishing attacks happened over a short period of time, but thanks to the potential for a site-wide rejection by other ISPs, it risked causing a major disruption to email service for university users.

Response

The straightforward response to phishing attacks delivered via Google Docs would seem to be reporting the incident to Google, but Stevens said that this approach proved futile. IT could report each phishing web form to Google's security team, but:

Unfortunately, you then need to wait for them to take action. Of late that seems typically to take a day or two; in the past it’s been much longer, sometimes on a scale of weeks. Most users are likely to visit the phishing form when they first see the email. After all it generally requires “urgent” action to avoid their account being shut down. So the responses will be within a few hours of the mails being sent, or perhaps the next working day. If the form is still up, they lose. As do you – within the next few days, you’re likely to find another spam run being dispatched from your email system.

Instead, the university decided to pull the plug on Google Docs from the university network, in the hopes that the outage would awaken users to the risk. "A temporary block would get users' attention and, we hoped, serve to moderate the 'chain reaction'."

Evidently the block did get users' attention—but IT failed to take into account how tightly Google Docs has become integrated with other Google services in recent years. The disruption to legitimate users was "greater than anticipated," causing Stevens's office to issue an apology and a detailed explanation of the problem.

On the other hand, Stevens did report that the temporary block accomplished its goal of short-circuiting the phishing attack. In the future, he said, the university would both search for a less disruptive way to circumvent Google Docs phishing attacks, and pressure Google to be "far more responsive, if not proactive, regarding abuse of their services for criminal activities." Google's slow reaction to reports of criminal activity has severe consequences for the university, he said.

We have to ask why Google, with the far greater resources available to them, cannot respond better. [...] Google may not themselves be being evil, but their inaction is making it easier for others to conduct evil activities using Google-provided services.

The 800 pound gorilla

So far, Google has not issued a public response to the Oxford incident. But one does not need to be a major university to find lessons in the story. First, the existence of web forms in Google Docs provides a nearly worldwide-accessible platform for mounting phishing attacks. Google's ubiquity has turned it into a de-facto "generic service" which many users may be oblivious to. In fact, Google Docs is widespread enough that many universities do use it to send out general polls, surveys, and other form-based questionnaires. Yes, the IT department is far less likely to employ a Google Docs form than is (for example) Human Resources, but that is the sort of detail it is all too easily missed by some small proportion of users on any particular email.

Second, Google's multi-day turnaround time for taking action against reported criminal activity is a problem in its own right. But while accurate reports of such criminal activity need to be acted on as soon as possible, the reality is that swift action raises the risk of false positives, too. Here again, Google services are so widespread now that it would be a challenge to police them all in real time. If, as Stevens suggested, Google were to automate any part of the form shutdown process, one nasty side effect would be that the automated process might turn into a vehicle for widespread denial of service instead.

Third, some will say that the sort of large-scale phishing attack seen at Oxford demonstrates that passwords alone are no longer sufficient for account security. But the university's tens of thousands of users present a daunting set of accounts to manage; supplying that many users with cryptographic security tokens or supporting that many users in a multi-factor authentication scheme would constitute a substantially higher cost than it would for most businesses—more so when one considers that the student population turns over regularly.

Of course, Oxford's experience is only one data point. In the Hacker News discussion of the event, commenter Jose Nazario pointed to a 2011 IEEE paper (and provided a PDF link for those without IEEE library access) he co-authored that examined the prevalence of form-based phishing attacks. Google Docs was the second-most popular host for form phishing attacks, and phishing forms based there lasted, on average, more than six days. The most widely-used service for form-based phishing attacks was addaform.com, and there were several others with numbers somewhat close to those of Google Docs.

The prospect of intercepting all form-based phishing is a daunting one, to be sure. But regardless of the precise rankings, eliminating the threat from Google Docs is likely to be far more difficult since, like Big Brother, Google services are everywhere.

Comments (31 posted)

Brief items

Security quotes of the week

A knife is allowed if:
  • The blade is no longer than 2.36 inches or 6 centimeters in length
  • The blade width is no more than ½ inch at its widest point
  • ...
-- US Transportation Security Administration [PDF] on new rules governing knives on planes using nice round numbers in two different measurement systems

Excommunication is like being fired, only it lasts for eternity.
-- Bruce Schneier

When conducting national security investigations, the U.S. Federal Bureau of Investigation can issue a National Security Letter (NSL) to obtain identifying information about a subscriber from telephone and Internet companies. The FBI has the authority to prohibit companies from talking about these requests. But we’ve been trying to find a way to provide more information about the NSLs we get—particularly as people have voiced concerns about the increase in their use since 9/11.

Starting today, we’re now including data about NSLs in our Transparency Report. We’re thankful to U.S. government officials for working with us to provide greater insight into the use of NSLs. Visit our page on user data requests in the U.S. and you’ll see, in broad strokes, how many NSLs for user data Google receives, as well as the number of accounts in question. In addition, you can now find answers to some common questions we get asked about NSLs on our Transparency Report FAQ.

-- Google shines a little light onto US government secrecy

This also goes for security people. If we had any sense we'd go live in the woods in a cabin and drink moonshine and go hunting. I'm still assigning CVE's for /tmp file vulns. That's just inexcusably stupid.
-- Kurt Seifried

Comments (4 posted)

New vulnerabilities

apache2: privilege escalation

Package(s):apache2 CVE #(s):CVE-2013-1048
Created:March 5, 2013 Updated:March 6, 2013
Description: From the Debian advisory:

Hayawardh Vijayakumar noticed that the apache2ctl script created the lock directory in an unsafe manner, allowing a local attacker to gain elevated privileges via a symlink attack. This is a Debian specific issue.

Alerts:
Debian DSA-2637-1 2013-03-04
Ubuntu USN-1765-1 2013-03-18

Comments (none posted)

cfingerd: code execution

Package(s):cfingerd CVE #(s):CVE-2013-1049
Created:March 1, 2013 Updated:March 6, 2013
Description:

From the Debian advisory:

Malcolm Scott discovered a remote-exploitable buffer overflow in the rfc1413 (ident) client of cfingerd, a configurable finger daemon. This vulnerability was introduced in a previously applied patch to the cfingerd package in 1.4.3-3.

Alerts:
Debian DSA-2635-1 2013-03-01

Comments (none posted)

drupal7: denial of service

Package(s):drupal7 CVE #(s):
Created:March 6, 2013 Updated:March 6, 2013
Description: Drupal 7.20, resolves SA-CORE-2013-002, a denial of service vulnerability.
Alerts:
Fedora FEDORA-2013-2862 2013-03-05
Fedora FEDORA-2013-2872 2013-03-05

Comments (none posted)

dtach: information disclosure

Package(s):dtach CVE #(s):CVE-2012-3368
Created:March 5, 2013 Updated:March 6, 2013
Description: From the Red Hat bugzilla:

A portion of memory (random stack data) disclosure flaw was found in the way dtach, a simple program emulating the detach feature of screen, performed client connection termination under certain circumstances. A remote attacker could use this flaw to potentially obtain sensitive information by issuing a specially-crafted dtach client connection close request.

Alerts:
Fedora FEDORA-2013-2923 2013-03-04

Comments (none posted)

ekiga: denial of service

Package(s):ekiga CVE #(s):CVE-2012-5621
Created:March 4, 2013 Updated:March 6, 2013
Description: From the Red Hat bugzilla:

A denial of service flaw was found in the way Ekiga, a Gnome based SIP/H323 teleconferencing application, processed information from certain OPAL connections (UTF-8 strings were not verified for validity prior showing them). A remote attacker (other party with a not UTF-8 valid name) could use this flaw to cause ekiga executable crash.

Alerts:
Fedora FEDORA-2013-2998 2013-03-03
Fedora FEDORA-2013-2890 2013-03-03
Fedora FEDORA-2013-2998 2013-03-03
Fedora FEDORA-2013-2890 2013-03-03
Fedora FEDORA-2013-2998 2013-03-03
Fedora FEDORA-2013-2890 2013-03-03

Comments (none posted)

git: information disclosure

Package(s):git CVE #(s):CVE-2013-0308
Created:March 4, 2013 Updated:March 18, 2013
Description: From the Red Hat advisory:

It was discovered that Git's git-imap-send command, a tool to send a collection of patches from standard input (stdin) to an IMAP folder, did not properly perform SSL X.509 v3 certificate validation on the IMAP server's certificate, as it did not ensure that the server's hostname matched the one provided in the CN field of the server's certificate. A rogue server could use this flaw to conduct man-in-the-middle attacks, possibly leading to the disclosure of sensitive information.

Alerts:
openSUSE openSUSE-SU-2013:0380-1 2013-03-01
openSUSE openSUSE-SU-2013:0382-1 2013-03-01
Fedora FEDORA-2013-2829 2013-03-02
Fedora FEDORA-2013-2763 2013-03-02
Red Hat RHSA-2013:0589-01 2013-03-04
Scientific Linux SL-git-20130304 2013-03-04
Oracle ELSA-2013-0589 2013-03-04
CentOS CESA-2013:0589 2013-03-09
Mageia MGASA-2013-0091 2013-03-16

Comments (none posted)

isync: information disclosure

Package(s):isync CVE #(s):CVE-2013-0289
Created:March 4, 2013 Updated:March 6, 2013
Description: From the Red Hat bugzilla:

A security flaw was found in the way isync, a command line application to synchronize IMAP4 and Maildir mailboxes, (previously) performed server's SSL x509.v3 certificate validation, when performing IMAP protocol based synchronization (server's hostname was previously not compared for match the CN field of the certificate). A rogue server could use this flaw to conduct man-in-the-middle (MiTM) attacks, possibly leading to disclosure of sensitive information.

Alerts:
Fedora FEDORA-2013-2795 2013-03-03
Fedora FEDORA-2013-2758 2013-03-03

Comments (none posted)

kernel: multiple vulnerabilities

Package(s):kernel CVE #(s):CVE-2013-0216 CVE-2013-0217
Created:March 1, 2013 Updated:March 22, 2013
Description:

From the Xen advisory:

The Xen netback implementation contains a couple of flaws which can allow a guest to cause a DoS in the backend domain, potentially affecting other domains in the system.

CVE-2013-0216 is a failure to sanity check the ring producer/consumer pointers which can allow a guest to cause netback to loop for an extended period preventing other work from occurring.

CVE-2013-0217 is a memory leak on an error path which is guest triggerable.

Alerts:
Oracle ELSA-2013-2507 2013-02-28
openSUSE openSUSE-SU-2013:0395-1 2013-03-05
openSUSE openSUSE-SU-2013:0396-1 2013-03-05
Ubuntu USN-1756-1 2013-03-06
Ubuntu USN-1760-1 2013-03-12
Ubuntu USN-1767-1 2013-03-18
Ubuntu USN-1769-1 2013-03-18
Ubuntu USN-1768-1 2013-03-18
Ubuntu USN-1774-1 2013-03-21
Fedora FEDORA-2013-3909 2013-03-22

Comments (none posted)

kernel: multiple vulnerabilities

Package(s):kernel CVE #(s):CVE-2013-1767 CVE-2013-1774
Created:March 4, 2013 Updated:March 22, 2013
Description: From the Mageia advisory:

Linux kernel is prone to a local privilege-escalation vulnerability due to a tmpfs use-after-free error. Local attackers can exploit the issue to execute arbitrary code with kernel privileges or to crash the kernel, effectively denying service to legitimate users (CVE-2013-1767).

Linux kernel built with Edgeport USB serial converter driver io_ti, is vulnerable to a NULL pointer dereference flaw. It happens if the device is disconnected while corresponding /dev/ttyUSB? file is in use. An unprivileged user could use this flaw to crash the system, resulting DoS (CVE-2013-1774).

Alerts:
Mageia MGASA-2013-0079 2013-03-02
Mageia MGASA-2013-0080 2013-03-02
Mageia MGASA-2013-0081 2013-03-02
Mageia MGASA-2013-0082 2013-03-02
Mageia MGASA-2013-0083 2013-03-02
Fedora FEDORA-2013-3223 2013-03-02
Ubuntu USN-1767-1 2013-03-18
Fedora FEDORA-2013-3909 2013-03-22
Ubuntu USN-1781-1 2013-03-26
Ubuntu USN-1787-1 2013-04-02

Comments (none posted)

kernel: multiple vulnerabilities

Package(s):kernel CVE #(s):CVE-2012-5374 CVE-2013-0160
Created:March 5, 2013 Updated:March 6, 2013
Description: From the CVE entries:

The CRC32C feature in the Btrfs implementation in the Linux kernel before 3.8-rc1 allows local users to cause a denial of service (extended runtime of kernel code) by creating many different files whose names are associated with the same CRC32C hash value. (CVE-2012-5374)

The Linux kernel through 3.7.9 allows local users to obtain sensitive information about keystroke timing by using the inotify API on the /dev/ptmx device. (CVE-2013-0160)

Alerts:
openSUSE openSUSE-SU-2013:0395-1 2013-03-05
openSUSE openSUSE-SU-2013:0396-1 2013-03-05

Comments (none posted)

kernel: privilege escalation/information leak

Package(s):kernel linux CVE #(s):CVE-2013-0349 CVE-2013-1773
Created:March 6, 2013 Updated:March 6, 2013
Description: From the Ubuntu advisory:

An information leak was discovered in the Linux kernel's Bluetooth stack when HIDP (Human Interface Device Protocol) support is enabled. A local unprivileged user could exploit this flaw to cause an information leak from the kernel. (CVE-2013-0349)

A flaw was discovered on the Linux kernel's VFAT filesystem driver when a disk is mounted with the utf8 option (this is the default on Ubuntu). On a system where disks/images can be auto-mounted or a FAT filesystem is mounted an unprivileged user can exploit the flaw to gain root privileges. (CVE-2013-1773)

Alerts:
Ubuntu USN-1756-1 2013-03-06
Red Hat RHSA-2013:0566-01 2013-03-06
Ubuntu USN-1760-1 2013-03-12
Ubuntu USN-1767-1 2013-03-18
Ubuntu USN-1769-1 2013-03-18
Ubuntu USN-1768-1 2013-03-18
Ubuntu USN-1775-1 2013-03-22
Ubuntu USN-1776-1 2013-03-22
Ubuntu USN-1778-1 2013-03-22
Ubuntu USN-1781-1 2013-03-26

Comments (none posted)

libxml2: denial of service

Package(s):libxml2 CVE #(s):CVE-2013-0338
Created:March 1, 2013 Updated:March 28, 2013
Description:

From the Red hat advisory:

A denial of service flaw was found in the way libxml2 performed string substitutions when entity values for entity references replacement was enabled. A remote attacker could provide a specially-crafted XML file that, when processed by an application linked against libxml2, would lead to excessive CPU consumption.

Alerts:
Red Hat RHSA-2013:0581-01 2013-02-28
Oracle ELSA-2013-0581 2013-02-28
CentOS CESA-2013:0581 2013-03-01
Scientific Linux SL-libx-20130228 2013-02-28
Oracle ELSA-2013-0581 2013-03-01
Mageia MGASA-2013-0085 2013-03-03
Mandriva MDVSA-2013:017 2013-03-05
CentOS CESA-2013:0581 2013-03-09
Debian DSA-2652-1 2013-03-26
openSUSE openSUSE-SU-2013:0552-1 2013-03-27
openSUSE openSUSE-SU-2013:0555-1 2013-03-27
Ubuntu USN-1782-1 2013-03-28

Comments (none posted)

nginx: world accessible directories

Package(s):nginx CVE #(s):CVE-2013-0337
Created:March 5, 2013 Updated:March 6, 2013
Description: From the Red Hat bugzilla:

Agostino Sarubbo reported on the oss-security mailing list that, on Gentoo, /var/log/nginx is world-accessible and the log files inside the directory are world-readable. This could allow an unprivileged user to read the log files.

Alerts:
Fedora FEDORA-2013-2974 2013-03-04
Fedora FEDORA-2013-2955 2013-03-04

Comments (none posted)

openafs: multiple vulnerabilities

Package(s):openafs CVE #(s):CVE-2013-1794 CVE-2013-1795
Created:March 5, 2013 Updated:March 6, 2013
Description: From the Scientific Linux advisory:

By carefully crafting an ACL entry an attacker may overflow fixed length buffers within the OpenAFS fileserver, crashing the fileserver, and potentially permitting the execution of arbitrary code. To perform the exploit, the attacker must already have permissions to create ACLs on the fileserver in question. Once such an ACL is present on a fileserver, client utilities such as 'fs' which manipulate ACLs, may be crashed when they attempt to read or modify the ACL.(CVE-2013-1794)

The ptserver accepts a list of unbounded size from the IdToName RPC. The length of this list is then used to determine the size of a number of other internal data structures. If the length is sufficiently large then we may hit an integer overflow when calculating the size to pass to malloc, and allocate data structures of insufficient length, allowing heap memory to be overwritten. This may allow an unauthenticated attacker to crash an OpenAFS ptserver. (CVE-2013-1795)

Alerts:
Scientific Linux SL-open-20130304 2013-03-04
Debian DSA-2638-1 2013-03-04

Comments (none posted)

openjdk-6: code execution

Package(s):openjdk-6 CVE #(s):CVE-2013-0809 CVE-2013-1493
Created:March 6, 2013 Updated:March 20, 2013
Description: From the CVE entries:

Unspecified vulnerability in the 2D component in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 15 and earlier, 6 Update 41 and earlier, and 5.0 Update 40 and earlier allows remote attackers to execute arbitrary code via unknown vectors, a different vulnerability than CVE-2013-1493. (CVE-2013-0809)

The color management (CMM) functionality in the 2D component in Oracle Java SE 7 Update 15 and earlier, 6 Update 41 and earlier, and 5.0 Update 40 and earlier allows remote attackers to execute arbitrary code or cause a denial of service (crash) via an image with crafted raster parameters, which triggers (1) an out-of-bounds read or (2) memory corruption in the JVM, as exploited in the wild in February 2013. (CVE-2013-1493)

Alerts:
Ubuntu USN-1755-1 2013-03-05
Red Hat RHSA-2013:0600-01 2013-03-06
Red Hat RHSA-2013:0601-01 2013-03-06
Red Hat RHSA-2013:0603-01 2013-03-06
Red Hat RHSA-2013:0602-01 2013-03-06
Red Hat RHSA-2013:0604-01 2013-03-06
Red Hat RHSA-2013:0605-01 2013-03-06
CentOS CESA-2013:0604 2013-03-06
CentOS CESA-2013:0603 2013-03-06
Fedora FEDORA-2013-3467 2013-03-06
Oracle ELSA-2013-0603 2013-03-07
Oracle ELSA-2013-0602 2013-03-06
Oracle ELSA-2013-0604 2013-03-07
Oracle ELSA-2013-0605 2013-03-06
Scientific Linux SL-java-20130307 2013-03-07
Scientific Linux SL-java-20130307 2013-03-07
Ubuntu USN-1755-2 2013-03-07
Mandriva MDVSA-2013:021 2013-03-08
CentOS CESA-2013:0605 2013-03-09
CentOS CESA-2013:0602 2013-03-09
Mageia MGASA-2013-0088 2013-03-09
Mageia MGASA-2013-0089 2013-03-09
Red Hat RHSA-2013:0624-01 2013-03-11
Red Hat RHSA-2013:0625-01 2013-03-11
Red Hat RHSA-2013:0626-01 2013-03-11
openSUSE openSUSE-SU-2013:0430-1 2013-03-12
openSUSE openSUSE-SU-2013:0438-1 2013-03-12
SUSE SUSE-SU-2013:0434-1 2013-03-12
Fedora FEDORA-2013-3468 2013-03-14
openSUSE openSUSE-SU-2013:0509-1 2013-03-20

Comments (none posted)

openstack-packstack: multiple vulnerabilities

Package(s):openstack-packstack CVE #(s):CVE-2013-0261 CVE-2013-0266
Created:March 6, 2013 Updated:March 6, 2013
Description: From the Red Hat advisory:

A flaw was found in PackStack. During manifest creation, the manifest file was written to /tmp/ with a predictable file name. A local attacker could use this flaw to perform a symbolic link attack, overwriting an arbitrary file accessible to the user running PackStack with the contents of the manifest, which could lead to a denial of service. Additionally, the attacker could read and potentially modify the manifest being generated, allowing them to modify systems being deployed using OpenStack. (CVE-2013-0261)

It was discovered that the cinder.conf and all api-paste.ini configuration files were created with world-readable permissions. A local attacker could use this flaw to view administrative passwords, allowing them to control systems deployed and managed by OpenStack. (CVE-2013-0266)

Alerts:
Red Hat RHSA-2013:0595-01 2013-03-05

Comments (none posted)

PackageKit: installs old package versions

Package(s):PackageKit CVE #(s):
Created:March 4, 2013 Updated:March 6, 2013
Description: From the openSUSE advisory:

PackageKit was fixed to add a patch to forbid update to downgrade (bnc#804983)

As the update operation is allowed for logged in regular users, they could install old package versions which might have been still affected by already fixed security problems.

Alerts:
openSUSE openSUSE-SU-2013:0381-1 2013-03-01

Comments (none posted)

php: two vulnerabilities

Package(s):php CVE #(s):CVE-2013-1635 CVE-2013-1643
Created:February 28, 2013 Updated:April 3, 2013
Description:

From the Mandriva advisory:

PHP does not validate the configration directive soap.wsdl_cache_dir before writing SOAP wsdl cache files to the filesystem. Thus an attacker is able to write remote wsdl files to arbitrary locations (CVE-2013-1635).

PHP allows the use of external entities while parsing SOAP wsdl files which allows an attacker to read arbitrary files. If a web application unserializes user-supplied data and tries to execute any method of it, an attacker can send serialized SoapClient object initialized in non-wsdl mode which will make PHP to parse automatically remote XML-document specified in the location option parameter (CVE-2013-1643).

Alerts:
Mandriva MDVSA-2013:016 2013-02-28
Debian DSA-2639-1 2013-03-05
Ubuntu USN-1761-1 2013-03-13
Slackware SSA:2013-081-01 2013-03-23
Mageia MGASA-2013-0101 2013-04-02
Fedora FEDORA-2013-3891 2013-04-03
Fedora FEDORA-2013-3927 2013-04-03

Comments (none posted)

ruby: denial of service

Package(s):ruby CVE #(s):
Created:March 6, 2013 Updated:March 6, 2013
Description: From the Ruby advisory:

Unrestricted entity expansion can lead to a DoS vulnerability in REXML. (The CVE identifier will be assigned later.) We strongly recommend to upgrade ruby.

When reading text nodes from an XML document, the REXML parser can be coerced in to allocating extremely large string objects which can consume all of the memory on a machine, causing a denial of service.

Alerts:
Fedora FEDORA-2013-3037 2013-03-05
Fedora FEDORA-2013-3038 2013-03-05

Comments (none posted)

rubygem-devise: unauthorized account access

Package(s):rubygem-devise CVE #(s):CVE-2013-0233
Created:March 4, 2013 Updated:March 6, 2013
Description: From the Novell bugzilla:

Using a specially crafted request, an attacker could trick the database type conversion code to return incorrect records. For some token values this could allow an attacker to bypass the proper checks and gain control of other accounts.

Alerts:
openSUSE openSUSE-SU-2013:0374-1 2013-03-01

Comments (none posted)

rubygem-ruby_parser: insecure file creation

Package(s):openshift CVE #(s):CVE-2013-0162
Created:March 1, 2013 Updated:March 6, 2013
Description:

From the Red Hat advisory:

It was found that ruby_parser from rubygem-ruby_parser created a temporary file in an insecure way. A local attacker could use this flaw to perform a symbolic link attack, overwriting arbitrary files accessible to the application using ruby_parser.

Alerts:
Red Hat RHSA-2013:0582-01 2013-02-28

Comments (none posted)

sudo: privilege escalation

Package(s):sudo CVE #(s):CVE-2013-1775
Created:February 28, 2013 Updated:March 20, 2013
Description:

From the Ubuntu advisory:

Marco Schoepl discovered that Sudo incorrectly handled time stamp files when the system clock is set to epoch. A local attacker could use this issue to run Sudo commands without a password prompt.

Alerts:
Ubuntu USN-1754-1 2013-02-28
Mageia MGASA-2013-0078 2013-03-01
Slackware SSA:2013-065-01 2013-03-06
Debian DSA-2642-1 2013-03-09
Mandriva MDVSA-2013:026 2013-03-18
Fedora FEDORA-2013-3297 2013-03-16
Fedora FEDORA-2013-3270 2013-03-19
openSUSE openSUSE-SU-2013:0495-1 2013-03-20
openSUSE openSUSE-SU-2013:0503-1 2013-03-20

Comments (none posted)

sudo: privilege escalation

Package(s):sudo CVE #(s):CVE-2013-1776
Created:March 4, 2013 Updated:March 20, 2013
Description: From the Mageia advisory:

Sudo before 1.8.6p7 allows a malicious user to run commands via sudo without authenticating, so long as there exists a terminal the user has access to where a sudo command was successfully run by that same user within the password timeout period (usually five minutes).

Alerts:
Mageia MGASA-2013-0078 2013-03-01
Slackware SSA:2013-065-01 2013-03-06
Debian DSA-2642-1 2013-03-09
Mandriva MDVSA-2013:026 2013-03-18
Fedora FEDORA-2013-3297 2013-03-16
Fedora FEDORA-2013-3270 2013-03-19
openSUSE openSUSE-SU-2013:0495-1 2013-03-20
openSUSE openSUSE-SU-2013:0503-1 2013-03-20

Comments (none posted)

yum: denial of service

Package(s):yum CVE #(s):
Created:March 4, 2013 Updated:March 18, 2013
Description: From the Fedora advisory:

Fix a DOS attack (maybe more) by a bad Fedora mirror on repo. metadata.

Alerts:
Fedora FEDORA-2013-2799 2013-03-02
Fedora FEDORA-2013-2789 2013-03-18

Comments (none posted)

Page editor: Jake Edge
Next page: Kernel development>>

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds