VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

DotNetCasClient: vulnerability history, versions and safety

DotNetCasClient is a package in the NuGet ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all DotNetCasClient vulnerabilities

Vulert verdict on DotNetCasClient 1.3.2 i

Updated on 23 Oct 2026

Good news: 1.3.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 71/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 1.3.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.3.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.3.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release 90 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by NuGet, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for DotNetCasClient, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.3.2 17 Apr 2019 none Apache-2.0 — Details →
1.3.1 17 Apr 2019 none Apache-2.0 — Details →
1.3.0 16 Apr 2019 none Apache-2.0 — Details →
1.2.0 06 Apr 2019 none Apache-2.0 — Details →
1.1.0 10 Aug 2017 none non-standard — Details →
1.0.2 03 Feb 2015 none non-standard — Details →
1.0.1 06 Apr 2011 C2 non-standard Yes Details →
1.0.0 28 Feb 2011 C2 non-standard Yes Details →

All 8 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for DotNetCasClient

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-4172: URL Parameter Injection Vulnerability in Jasig Java CAS Client, .NET CAS Client, and phpCAS 9.8 critical 1.0.2 17 May 2022
CVE-2014-4172: URL Parameter Injection Vulnerability in Jasig Java CAS Client, .NET CAS Client, and phpCAS 9.8 critical 1.0.2 17 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About DotNetCasClient

Is DotNetCasClient safe to use?

Vulert records 2 vulnerabilities for DotNetCasClient in NuGet: 2 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is DotNetCasClient's Vulert package health score?

Vulert scores DotNetCasClient 71/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of DotNetCasClient affected?

No. 1.3.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of DotNetCasClient should I use?

1.3.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does DotNetCasClient have?

2 vulnerabilities are recorded for DotNetCasClient in the NuGet ecosystem: 2 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new DotNetCasClient vulnerabilities disclosed?

0 vulnerabilities were recorded for DotNetCasClient in the last 12 months, and the oldest entry in this database dates to 17 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of DotNetCasClient are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor DotNetCasClient for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the DotNetCasClient version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.