VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

asterix-decoder: vulnerability history, versions and safety

asterix-decoder is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 36 releases, from Nov 2021 to 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 H1 U1
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 asterix-decoder vulnerabilities

Vulert verdict on asterix-decoder 0.7.11 i

Updated on 23 Oct 2026

Action needed: 0.7.11 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 65/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.7.11 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Stars 214 i
  • OpenSSF scorecard 3/10 i
  • Last release 10 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 asterix-decoder, 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
0.7.11 03 Dec 2025 U1 non-standard Yes Details →
0.7.10 24 Oct 2025 U1 non-standard Yes Details →
0.7.9 21 Feb 2025 U1 non-standard Yes Details →
0.7.8 14 Nov 2024 U1 non-standard Yes Details →
0.7.7 23 Aug 2024 U1 non-standard Yes Details →
0.7.6 25 Mar 2024 U1 non-standard Yes Details →
0.7.5 04 Dec 2023 U1 non-standard Yes Details →
0.7.4 20 Jul 2022 U1 non-standard Yes Details →
0.7.3 05 Apr 2022 U1 non-standard Yes Details →
0.7.2 23 Nov 2021 U1 non-standard Yes Details →
0.7.1 20 May 2021 H1 U1 non-standard Yes Details →
0.7.0 12 Feb 2021 H1 U1 non-standard Yes Details →
0.6.1 25 Nov 2020 H1 U1 non-standard Yes Details →
0.6.0 02 Oct 2020 H1 U1 non-standard Yes Details →
0.5.16 26 Aug 2020 H1 U1 non-standard Yes Details →
0.5.15 15 May 2020 H1 U1 non-standard Yes Details →
0.5.14 10 Apr 2020 H1 U1 non-standard Yes Details →
0.5.13 10 Mar 2020 H1 U1 non-standard Yes Details →
0.5.12 21 Nov 2019 H1 U1 non-standard Yes Details →
0.5.11 16 Oct 2019 H1 U1 non-standard Yes Details →
0.5.10 29 Aug 2019 H1 U1 non-standard Yes Details →
0.5.9 08 Feb 2019 H1 U1 non-standard Yes Details →
0.5.8 30 Oct 2018 H1 U1 non-standard Yes Details →
0.5.7 29 Oct 2018 H1 U1 non-standard Yes Details →
0.5.6 12 Oct 2018 H1 U1 non-standard Yes Details →
0.5.5 24 Jul 2018 H1 U1 non-standard Yes Details →
0.5.2 19 Apr 2018 H1 U1 non-standard Yes Details →
0.5.1 23 Mar 2018 H1 U1 non-standard Yes Details →
0.5.0 21 Sep 2017 H1 U1 non-standard Yes Details →
0.4.2 17 May 2017 H1 U1 non-standard Yes Details →
0.4.1 17 Apr 2017 H1 U1 non-standard Yes Details →
0.4.0 15 Apr 2017 H1 U1 non-standard Yes Details →
0.3.0 18 Jan 2017 H1 U1 non-standard Yes Details →
0.2.0 29 Aug 2016 H1 U1 non-standard Yes Details →
0.1.0 16 Aug 2016 H1 U1 non-standard Yes Details →
0.4.0-py2.6-linux-x86_64 — H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1

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 asterix-decoder

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-44144: Asterix Heap-based Buffer Overflow in asterix-decoder 9.1 high 0.7.2 24 May 2022
CVE-2021-44144: Heap-based Buffer Over-read in Croatia Control Asterix 2.8.1 N/A unrated 3f765d387d239ccc44e278a2ffa600fb6a6587f9 22 Nov 2021

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 asterix-decoder

Is asterix-decoder safe to use?

Vulert records 2 vulnerabilities for asterix-decoder in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is asterix-decoder's Vulert package health score?

Vulert scores asterix-decoder 65/100, which reads as usable, but worth attention. 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 asterix-decoder affected?

Yes. 0.7.11, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of asterix-decoder should I use?

0.7.11 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 asterix-decoder have?

2 vulnerabilities are recorded for asterix-decoder in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new asterix-decoder vulnerabilities disclosed?

0 vulnerabilities were recorded for asterix-decoder in the last 12 months, and the oldest entry in this database dates to 22 Nov 2021. 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 asterix-decoder 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 asterix-decoder for upcoming vulnerabilities?

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