Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 12 Apr 2012 13:46:16 +0200
From: Jan Lieskovsky <>
To: David Black <>
Subject: Re: CVE request: cobbler lack of csrf protection,
 code execution

Thank you for this post, David.

Just administrative note -- all of these security issues should
get CVE-2011-* CVE identifiers, as all of the Ubuntu bugs have
been reported in 2011 yet (2011-09-28 exactly).

On 04/12/2012 11:39 AM, David Black wrote:
> Hi, I reported some bugs a while ago in cobbler which never received
> CVE ID, could the follow bugs receive CVE ID ?
> 1. lack of csrf protection in the cobbler web interface (vulnerable to
> csrf attacks)

Some further references / patches information I was able to found:
1) Ubuntu patch by Robie Basak:

2) Red Hat bugzilla entry:

> 2. code execution on the cobbler host through use of yaml.loads on
> potentially untrusted user input

Though only yaml.load privilege escalation vector has been mentioned in this
post, from further look noticed two ways for privilege escalation:
1) (possibly remote) privilege escalation via yaml.load / by
    processing management parameters:

    References: (Ubuntu bug)

    Ubuntu patch from Robie Basak:
    * Backport safe YAML load from upstream. (LP: #858883): (Red Hat bug)

2) local privilege escalation due to insecure use of PYTHON_EGG_CACHE location:

    References: (Ubuntu bug) (upstream ticket)
    (relevant upstream patch) (Red Hat bug)

Kurt, could you allocate three 2011 CVE ids for these issues?
i)   the first for CSRF issue,
ii)  the second for the yaml.load priv esc issue,
iii) the third for the PYTHON_EGG_CACHE local priv esc issue

David, would be great if you could confirm the three ids are necessary.

Thank you && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Response Team

> --
> Thank you.

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.