.NET Misconfiguration: Use of Impersonation
CWE-520
Allowing a.NET application to run at potentially escalated levels of access to the underlying operating and file systems can be dangerous and result in various forms of attacks.
We track 4 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 7.5.
How this weakness is prevented
- Operation: Run the application with limited privilege to the underlying operating and file system.
Latest .NET Misconfiguration: Use of Impersonation vulnerabilities
- 8.1 High severity
Langflow OSS: .NET Misconfiguration: Use of Impersonation
IBM Langflow OSS 1.0.0 through 1.10.1 can allow an attacker to access another user's private vector documents by creating their own flow with matching Chroma persist_directory and collection_name values. The attacker receives exact victim content in their work
- 7.1 High severity
Langflow OSS: .NET Misconfiguration: Use of Impersonation
IBM Langflow OSS 1.0.0 through 1.10.1 can allow an attacker to reuse another user's FAISS namespace to access owner-only vector content and influence later query results. This causes cross-user information disclosure and limited integrity impact through persis
- 7.4 High severity
upKeeper Instant Privilege Access: .NET Misconfiguration: Use of Impersonation
.NET misconfiguration: use of impersonation vulnerability in upKeeper Solutions upKeeper Instant Privilege Access allows Hijacking a Privileged Thread of Execution.This issue affects upKeeper Instant Privilege Access: through 1.5.0.
- 7.5 High severity
aaa: .NET Misconfiguration: Use of Impersonation
An issue was discovered in OpenDaylight Authentication, Authorization and Accounting (AAA) through 0.19.3. A rogue controller can join a cluster to impersonate an offline peer, even if this rogue controller does not possess the complete cluster configuration i