Insertion of Sensitive Information Into Debugging Code Affecting case-utils package, versions [0.5.0,0.5.1)[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.0,0.10.1)[0.11.0,0.11.1)[0.12.0,0.12.1)[0.13.0,0.13.1)[0.14.0,0.14.1)

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

A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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.

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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 some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.

There is no loss of integrity within the impacted component.

There is no impact to availability within the impacted component.