Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2020.1804
Drupal core - Moderately critical - Cross Site Scripting - SA-CORE-2020-002
21 May 2020
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Drupal Core
Publisher: Drupal
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Cross-site Scripting -- Remote with User Interaction
Resolution: Patch/Upgrade
CVE Names: CVE-2020-11023 CVE-2020-11022
Original Bulletin:
https://www.drupal.org/sa-core-2020-002
- --------------------------BEGIN INCLUDED TEXT--------------------
Drupal core - Moderately critical - Cross Site Scripting - SA-CORE-2020-002
Project: Drupal core
Date: 2020-May-20
Security risk: Moderately critical 10â\x{136}\x{149}25
AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Uncommon
Vulnerability: Cross Site ScriptingDescription:
The jQuery project released version 3.5.0, and as part of that, disclosed two
security vulnerabilities that affect all prior versions. As mentioned in the
jQuery blog , both are
[...] security issues in jQuery's DOM manipulation methods, as in .html() ,
.append() , and the others. Security advisories for both of these issues
have been published on GitHub.
Those advisories are:
o CVE-2020-11022
o CVE-2020-11023
These vulnerabilities may be exploitable on some Drupal sites. This Drupal
security release backports the fixes to the relevant jQuery functions, without
making any other changes to the jQuery version that is included in Drupal core
or running on the site via some other module such as jQuery Update . It is not
necessary to update jquery_update on Drupal 7 sites that have the module
installed.
Backwards-compatibility code has also been added to minimize regressions to
Drupal sites that might rely on jQuery's prior behavior. With jQuery 3.5,
incorrect self-closing HTML tags in JavaScript for elements where end tags are
normally required will encounter a change in what jQuery returns or inserts .
To minimize that disruption in 8.8.x and earlier, this security release retains
jQuery's prior behavior for most safe tags. There may still be regressions for
edge cases, including invalidly self-closed custom elements on Internet
Explorer.
(Note: the backwards compatibility layer will not be included in the upcoming
Drupal 8.9 and 9.0 releases, so Drupal 8 and 9 modules, themes, and sites
should correct tags in JavaScript to properly use closing tags.)
If you find a regression caused by the jQuery changes, please report it in
Drupal core's issue queue (or that of the relevant contrib project). However,
if you believe you have found a security issue, please report it privately to
the Drupal Security Team .
Solution:
Install the latest version:
o If you are using Drupal 8.8, upgrade to Drupal 8.8.6 .
o If you are using Drupal 8.7, upgrade to Drupal 8.7.14 .
o If you are using Drupal 7, upgrade to Drupal 7.70 .
Versions of Drupal 8 prior to 8.7 are end-of-life and do not receive security
coverage. Sites on 8.6 or earlier should update to 8.7.14.
The pre-release Drupal versions (8.9 and 9.0) have been updated jQuery to
version 3.5.1 as of 8.9.0-beta3 and 9.0.0-beta3.
Reported By:
o Drew Webber of the Drupal Security Team
o Emerson Jair Reis Oliveira da Silva
Fixed By:
o Drew Webber of the Drupal Security Team
o Sally Young
o cilefen of the Drupal Security Team
o Jess of the Drupal Security Team
o Emerson Jair Reis Oliveira da Silva
o Lee Rowlands of the Drupal Security Team
o Alex Bronstein of the Drupal Security Team
o Ben Mullins
o Lauri Eskola
o Peter Weber
o Samuel Mortenson of the Drupal Security Team
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBXsYAZ+NLKJtyKPYoAQhrMA/+PYxw0oGCM2CUiKm6Y5VQxEB4nbndLcGQ
Izf73wOmnYn0tawT0rMPXxY+dIhuufOldTeMbT2qnR1K0OsT1t9j7CZF4/ypF+M7
7ra3FNyYSzhgYSYkC1WPPuFLDMBnbuqFspBi3L7Eu+SFJvcLvH2GVM7Qpf6HtL24
ba7MYg2Sdj0UQp6gKyyoYkhwqLCHaBWQenvDou3i9EasTO6u9WFFKYNcEJUVeYPm
fYDXtJDl5+pXFytDKh1UsZ5ydN7l0BcWcAvMs8hcFLTSV3yypoXlkwRqkrX5USIq
eJIMzGPDFbb6/SLS8GBlNXqaoKuy36RANCUAebqHcDdYGCNl/QSGJfRhxf2vfTZ2
6NBdsREgDt6Y2TFv3PfVYOoGg41x4iSENSOeECfjEr6iSJYISpEAH6H9rT/ZWB2M
E2hXZfHD0LNzBwFIGOx10Cs+cI0nO+F81OUGUOkTyhIwcy1JGCmiBPZewq2bbLBv
2t/aLFRA1pLxerKmsZ98Ov0tmZLNAGnfX0KMIA7+JxTcLCvvdJOYaZQ+0bDCTgb7
0fj/pcJiJ7LsIpkyGOK1hlWenHliKdck91gU58kV1q0E/IDf7qxQXOqfZrFVNfpq
uoxfImTF34qtcGxsymVK5yHIzWuyC00QodFDUAqvffrI0tvxsjhFA2XBbs4jsGCN
wkPRMmfu8Ow=
=dPOO
-----END PGP SIGNATURE-----