October 15, 2019
SLUB Event Registration Extension is prone to an arbitrary-file-upload vulnerability. A remote attacker can leverage this issue to execute arbitrary code within the context of the application, upload arbitrary code and execute it and execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may let the attacker steal cookie-based authentication credentials and launch other attacks. . SLUB Event Registration Extension version 3.0.2 and prior are vulnerable.
- SLUB Event Registration 1.1.0
- SLUB Event Registration 1.2.0
- SLUB Event Registration 1.2.2
- SLUB Event Registration 1.4.0
- SLUB Event Registration 2.2.0
- SLUB Event Registration 2.3.0
- SLUB Event Registration 2.4.0
- SLUB Event Registration 2.4.1
- SLUB Event Registration 2.4.2
- SLUB Event Registration 2.4.3
- SLUB Event Registration 3.0.0
- SLUB Event Registration 3.0.1
- SLUB Event Registration 3.0.2
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.
Run all software as a nonprivileged user with minimal access rights.
To limit the consequences of a successful exploit, run server processes within a restricted environment using facilities such as chroot or jail.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.
Updates are available. Please see the references or vendor advisory for more information.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.