REDHAT-BUG-1552060
First published: Tue Mar 06 2018(Updated: )
Case insensitive string comparison uses an insecure hashing algorithm which can be compromised in .NET Core 1.x (Unix) and .NET Core 2.0. The attack vector could be a Dictionary which uses case invariant keys.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft .NET Core Runtime | >=1.0<2.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of REDHAT-BUG-1552060?
The severity of REDHAT-BUG-1552060 is considered critical due to the potential for exploitation in case insensitive string comparisons.
How do I fix REDHAT-BUG-1552060?
To fix REDHAT-BUG-1552060, upgrade to .NET Core version 2.1 or later, which addresses the insecure hashing algorithm.
Which versions of .NET Core are affected by REDHAT-BUG-1552060?
REDHAT-BUG-1552060 affects .NET Core versions 1.x and 2.0.
What are the potential risks of not addressing REDHAT-BUG-1552060?
Not addressing REDHAT-BUG-1552060 could lead to vulnerabilities that allow attackers to compromise applications using insecure hashing for case invariant dictionary keys.
Is REDHAT-BUG-1552060 specific to Unix systems?
Yes, REDHAT-BUG-1552060 specifically affects .NET Core running on Unix systems.
- agent/references
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2018-0875
- agent/last-modified-date
- agent/type
- agent/severity
- agent/description
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/microsoft .net core runtime