Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 1.22% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2021
CVE-2021-34532High confidence
ASP.NET Core and Visual Studio Information Disclosure Vulnerability
Microsoft · ASP.NET Core 2.1
5.5MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 10 Aug 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft ASP.NET Core 2.1 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| NuGetMicrosoft.AspNetCore.Authentication.JwtBearer | ECOSYSTEM: introduced 2.1.0; fixed 2.1.29 | 2.1.29 | OSV record ↗aggregator derived · 11 Aug 2026 |
| NuGetMicrosoft.AspNetCore.Authentication.JwtBearer | ECOSYSTEM: introduced 3.0.0; fixed 3.1.18 | 3.1.18 | OSV record ↗aggregator derived · 11 Aug 2026 |
| NuGetMicrosoft.AspNetCore.Authentication.JwtBearer | ECOSYSTEM: introduced 5.0.0; fixed 5.0.9 | 5.0.9 | OSV record ↗aggregator derived · 11 Aug 2026 |
| nugetMicrosoft.AspNetCore.Authentication.JwtBearer | >= 3.0.0, < 3.1.18 | 3.1.18 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.AspNetCore.Authentication.JwtBearer | >= 5.0.0, < 5.0.9 | 5.0.9 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.AspNetCore.Authentication.JwtBearer | >= 2.1.0, < 2.1.29 | 2.1.29 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
ASP.NET Core and Visual Studio Information Disclosure Vulnerability
What
ASP.NET Core and Visual Studio Information Disclosure Vulnerability
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.
What
ASP.NET Core and Visual Studio Information Disclosure Vulnerability
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → vulnerable operation → obtain information outside the intended access boundary
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration. - CWE not yet assigned
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- ASP.NET Core 2.1: 2.0 < 2.1.29
- ASP.NET Core 3.1: 3.0 < 3.1.18
- ASP.NET Core 5.0: 5.0 < 5.0.9
- Microsoft Visual Studio 2019 version 16.10 (includes 16.0 - 16.9): 16.10.0 < 16.10.5
- Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3): 16.0 < 16.4.25
- Microsoft Visual Studio 2019 version 16.7 (includes 16.0 – 16.6): 16.0.0 < 16.7.18
- Microsoft Visual Studio 2019 version 16.9 (includes 16.0 - 16.8): 15.0.0 < 16.9.10
- Visual Studio 2019 for Mac version 8.10: 8.1.0 < 8.10.7
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 12 Aug 2021 · Last source change 10 Aug 2026, 15:10 UTC · CWE not yet assigned
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2021-1835
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.