Request is an http client. If a request is made using multipart, and the body type is a number, then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 || >2.51.0 <=2.67.0.
Weakness
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Request |
Request_project |
2.2.6 (including) |
2.47.0 (excluding) |
| Request |
Request_project |
2.51.0 (excluding) |
2.67.0 (including) |
| Node-request |
Ubuntu |
artful |
* |
| Node-request |
Ubuntu |
trusty |
* |
| Node-request |
Ubuntu |
upstream |
* |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References