httparty before 0.21.0 is vulnerable to an assumed-immutable web parameter vulnerability. A remote and unauthenticated attacker can provide…
httparty before 0.21.0 is vulnerable to an assumed-immutable web parameter vulnerability. A remote and unauthenticated attacker can provide a crafted filename parameter during multipart/form-data uploads which could result in attacker controlled filenames being written.
The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.
https://cwe.mitre.org/data/definitions/472.html →Open in CWE collection →This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
https://capec.mitre.org/data/definitions/31.html →Open in CAPEC collection →In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.
https://capec.mitre.org/data/definitions/39.html →Open in CAPEC collection →An adversary corrupts or modifies the content of XML schema information passed between a client and server for the purpose of undermining the security of the target. XML Schemas provide the structure and content definitions for XML documents. Schema poisoning is the ability to manipulate a schema either by replacing or modifying it to compromise the programs that process documents that use this schema.
https://capec.mitre.org/data/definitions/146.html →Open in CAPEC collection →An attacker manipulates an existing credential in order to gain access to a target application. Session credentials allow users to identify themselves to a service after an initial authentication without needing to resend the authentication information (usually a username and password) with every message. An attacker may be able to manipulate a credential sniffed from an existing connection in order to gain access to a target server.
https://capec.mitre.org/data/definitions/226.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| ruby-httparty | Tracked | |
| debian_linux | * | Tracked |
| fedora | * | Tracked |
| httparty | * | Tracked |