Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper handling of Cookies when using Cook…
Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. This issue arises from the manner in which the objects are initialized.
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
https://cwe.mitre.org/data/definitions/1321.html →Open in CWE collection →In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
https://capec.mitre.org/data/definitions/1.html →Open in CAPEC collection →This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
https://capec.mitre.org/data/definitions/77.html →Open in CAPEC collection →An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
https://capec.mitre.org/data/definitions/180.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| eap7-activemq-artemis | Tracked | |
| eap7-activemq-artemis | Tracked | |
| eap7-activemq-artemis | Tracked | |
| eap7-bouncycastle | Tracked | |
| eap7-bouncycastle | Tracked | |
| eap7-bouncycastle | Tracked | |
| eap7-hal-console | Tracked | |
| eap7-hal-console | Tracked | |
| eap7-hal-console | Tracked | |
| eap7-hibernate | Tracked | |
| eap7-hibernate | Tracked | |
| eap7-hibernate | Tracked | |
| eap7-ironjacamar | Tracked | |
| eap7-ironjacamar | Tracked | |
| eap7-ironjacamar | Tracked | |
| eap7-jboss-marshalling | Tracked | |
| eap7-jboss-marshalling | Tracked | |
| eap7-jboss-marshalling | Tracked | |
| eap7-jboss-modules | Tracked | |
| eap7-jboss-modules | Tracked |