Vulnerability Note VU#110532
Subrion CMS vulnerable to SQL injection by an authenticated user
Original Release date: 08 May 2015 | Last revised: 08 May 2015

Overview
Subrion CMS is vulnerable to SQL injection from authenticated users when a browser cookie is modified in a certain way.

Description
Subrion is an open source web-based content management system (CMS). Subrion is vulnerable to SQL injection due to deserialization of untrusted data from a browser cookie.
CWE-502: Deserialization of Untrusted Data
CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)

Upon user login, Subrion attempts to locate a cookie named salt and deserialize the cookie for use in SQL UPDATE statements when interacting with Subrion. Modifying this cookie in a certain way may result in arbitrary SQL statements being executed on Subrion’s underlying database.

This issue is verified in version 3.3.0. Other versions prior to 3.3.3 may also be affected. The reporter suggests versions as early as 3.1.1 may be affected.

Impact
An authenticated remote user may execute arbitrary SQL statements on Subrion’s database.

Solution
Apply an update

Subrion has released version 3.3.3 addressing this issue. Affected users are encouraged to update as soon as possible.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate UpdatedSubrionAffected03 Apr 201520 Apr 2015If you are a vendor and your product is affected, let
us know.

CVSS Metrics (Learn More)

Group
Score
Vector

Base
9.0
AV:N/AC:L/Au:S/C:C/I:C/A:C

Temporal
7.0
E:POC/RL:OF/RC:C

Environmental
5.3
CDP:ND/TD:M/CR:ND/IR:ND/AR:ND

References

http://www.subrion.org/forums/threads/subrion-cms-3-3-3-is-available.2024/

Credit

Thanks to Jack Baker for reporting this vulnerability to us, and to Subrion for quickly addressing this issue.
This document was written by Garret Wassermann.

Other Information

CVE IDs:
Unknown

Date Public:
27 Apr 2015

Date First Published:
08 May 2015

Date Last Updated:
08 May 2015

Document Revision:
46

FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.

Leave a Reply