327 matches found
shiro: Cookie padding oracle vulnerability with default configuration
Apache Shiro before 1.4.2, when using the default "remember me" configuration, cookies could be susceptible to a padding attack...
Insecure Session Management
Symfony uses an insecure session management. An attacker is able to authenticate as a privileged user on sites with user registration and the remember me login functionality enabled...
Improper authentication in Symfony
In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, a vulnerability would allow an attacker to authenticate as a privileged user on sites with user registration and remember me login functionality enabled. This is related to symfony/securit...
GHSA-R679-M633-G7WC Improper input validation in Apache Shiro
Apache Shiro before 1.4.2, when using the default "remember me" configuration, cookies could be susceptible to a padding attack...
Harded Coded Remember-Me Cookie
Opencast uses a harded coded remember-me cookie. The remember-me cookie is created by hashing the username, password, and an additional system key, allowing anyone with an access to the remember-me token for one server to compromise all servers using the same credentials...
Authentication Bypass
opencast-kernel is vulnerable to authentication bypass. The vulnerability exists as a fake remember-me token can be used to gain access of arbitrary users without the need to be authenticated...
CVE-2020-5206
In Opencast before 7.6 and 8.1, using a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access. This way, an attacker can, for example...
Authentication flaw
In Opencast before 7.6 and 8.1, using a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access. This way, an attacker can, for example...
CVE-2020-5206
Opencast prior to versions 7.6 and 8.1 was vulnerable to an authentication bypass: a fake remember-me token could be accepted as a valid login for a user (even if the token was incorrect) because the attacked endpoint allowed anonymous access. This could let an attacker impersonate a user, includ...
CVE-2020-5206 Authentication Bypass For Endpoints With Anonymous Access in OpenCast
In Opencast before 7.6 and 8.1, using a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access. This way, an attacker can, for example...
GHSA-MH8G-HPRG-8363 Hard-Coded Key Used For Remember-me Token in Opencast
Impact The security configuration in etc/security/mhdefaultorg.xml enables a remember-me cookie based on a hash created from the username, password, and an additional system key. Opencast has hard-coded this system key in the large XML file and never mentions to change this, basically ensuring th...
Hard-Coded Key Used For Remember-me Token in Opencast
Impact The security configuration in etc/security/mhdefaultorg.xml enables a remember-me cookie based on a hash created from the username, password, and an additional system key. Opencast has hard-coded this system key in the large XML file and never mentions to change this, basically ensuring th...
GHSA-VMM6-W4CF-7F3X Authentication Bypass For Endpoints With Anonymous Access in Opencast
Impact Using a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access. This way, an attacker can, for example, fake a remember-me toke...
Authentication Bypass For Endpoints With Anonymous Access in Opencast
Impact Using a remember-me cookie with an arbitrary username can cause Opencast to assume proper authentication for that user even if the remember-me cookie was incorrect given that the attacked endpoint also allows anonymous access. This way, an attacker can, for example, fake a remember-me toke...
CVE-2020-5222
Opencast before 7.6 and 8.1 enables a remember-me cookie based on a hash created from the username, password, and an additional system key. This means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials...
CVE-2020-5222
Opencast before 7.6 and 8.1 enables a remember-me cookie based on a hash created from the username, password, and an additional system key. This means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials...
Default credentials
Opencast before 7.6 and 8.1 enables a remember-me cookie based on a hash created from the username, password, and an additional system key. This means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials...
CVE-2020-5222
Opencast prior to 7.6 and 8.1 uses a remember-me cookie whose value is derived from a hash of the username, password, and a system key. If an attacker obtains a remember-me token from one server, they can access other servers that accept the same credentials without handling credentials. The issu...
CVE-2020-5222 Hard-Coded Key Used For Remember-me Token in OpenCast
Opencast before 7.6 and 8.1 enables a remember-me cookie based on a hash created from the username, password, and an additional system key. This means that an attacker getting access to a remember-me token for one server can get access to all servers which allow log-in using the same credentials...
The vulnerability of the Apache Shiro framework, related to the default use of the “remember me” configuration, allows attackers to compromise the integrity of cookies.
The vulnerability of the Apache Shiro framework is related to the default use of the “remember me” configuration. Exploiting this vulnerability allows a malicious actor to affect the integrity of cookie files...