Insertion of Sensitive Information into Log File Affecting aws-sigv4 package, versions >=0.2.0 <0.2.1>=0.3.0 <0.3.1>=0.4.1 <0.4.2>=0.5.2 <0.5.3>=0.6.0 <0.6.1>=0.7.0 <0.7.1>=0.8.0 <0.8.1>=0.9.0 <0.9.1>=0.10.1 <0.10.2>=0.11.0 <0.11.1>=0.12.0 <0.12.1>=0.13.0 <0.13.1>=0.14.0 <0.14.1>=0.15.0 <0.15.1>=0.46.0 <0.46.1>=0.47.0 <0.47.1>=0.48.0 <0.48.1>=0.49.0 <0.49.1>=0.50.0 <0.50.1>=0.51.0 <0.51.1>=0.52.0 <0.52.1>=0.53.1 <0.53.2>=0.54.1 <0.54.2>=0.55.0 <0.55.1

The vulnerable component is not bound to the network stack and the attacker's path is via read/write/execute capabilities.

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

The vulnerable system can be exploited without interaction from any user.

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

There is no loss of integrity within the impacted component.

There is no impact to availability within the impacted component.