Lucene search

K
osvGoogleOSV:DSA-2246-1
HistoryMay 29, 2011 - 12:00 a.m.

mahara - several vulnerabilities

2011-05-2900:00:00
Google
osv.dev
5

6.8 Medium

CVSS2

Access Vector

NETWORK

Access Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:M/Au:N/C:P/I:P/A:P

0.004 Low

EPSS

Percentile

70.8%

Several vulnerabilities were discovered in Mahara, an electronic portfolio,
weblog, and resume builder. The Common Vulnerabilities and
Exposures project identifies the following problems:

  • CVE-2011-1402
    It was discovered that previous versions of Mahara did not check user
    credentials before adding a secret URL to a view or suspending a user.
  • CVE-2011-1403
    Due to a misconfiguration of the Pieform package in Mahara, the cross-site
    request forgery protection mechanism that Mahara relies on to harden its
    form was not working and was essentially disabled.
    This is a critical vulnerability which could allow attackers to trick other
    users (for example administrators) into performing malicious actions on
    behalf of the attacker. Most Mahara forms are vulnerable.
  • CVE-2011-1404
    Many of the JSON structures returned by Mahara for its AJAX interactions
    included more information than what ought to be disclosed to the logged in
    user. New versions of Mahara limit this information to what is necessary for
    each page.
  • CVE-2011-1405
    Previous versions of Mahara did not escape the contents of HTML emails sent
    to users. Depending on the filters enabled in one’s mail reader, it could
    lead to cross-site scripting attacks.
  • CVE-2011-1406
    It has been pointed out to us that if Mahara is configured (through its
    wwwroot variable) to use HTTPS, it will happily let users login via the HTTP
    version of the site if the web server is configured to serve content over
    both protocol. The new version of Mahara will, when the wwwroot points to an
    HTTPS URL, automatically redirect to HTTPS if it detects that it is being
    run over HTTP.

We recommend that sites wanting to run Mahara over HTTPS make sure that
their web server configuration does not allow the serving of content over
HTTP and merely redirects to the secure version. We also suggest that site
administrators consider adding the HSTS
headers
to their web server configuration.

For the oldstable distribution (lenny), these problems have been fixed in
version 1.0.4-4+lenny10.

For the stable distribution (squeeze), these problems have been fixed in
version 1.2.6-2+squeeze2.

For the testing distribution (wheezy), these problems have been fixed in
version 1.3.6-1.

For the unstable distribution (sid), these problems have been fixed in
version 1.3.6-1.

We recommend that you upgrade your mahara packages.

CPENameOperatorVersion
maharaeq1.2.6-2
maharaeq1.2.6-2+squeeze1

6.8 Medium

CVSS2

Access Vector

NETWORK

Access Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:M/Au:N/C:P/I:P/A:P

0.004 Low

EPSS

Percentile

70.8%