VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

openssl1.0: vulnerability history, versions and safety

openssl1.0 is a package in the Debian ecosystem. Vulert records 13 vulnerabilities for it across 23 releases, from Nov 2017 to Mar 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded U13
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 openssl1.0 vulnerabilities

Vulert verdict on openssl1.0 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 17 Mar 2022. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 13 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 13 over 4 years · 0 in the last year i
  • Latest disclosure 17 Mar 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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 holds for openssl1.0, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 23 of 23 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 2
  • 2019 3
  • 2020 2
  • 2021 3
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for openssl1.0

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
OpenSSL1.0 - Padding Oracle Attack N/A unrated 1.0.2r-1~deb9u1 28 Feb 2019
OpenSSL1.0 - Security Update N/A unrated 1.0.2l-2+deb9u2 17 Dec 2017
OpenSSL1.0 - Denial of Service Vulnerability N/A unrated 1.0.2l-2+deb9u3 29 Mar 2018
OpenSSL1.0 - Local Side Channel Attacks and Denial of Service Vulnerability N/A unrated 1.0.2q-1~deb9u1 19 Dec 2018
OpenSSL1.0 - Security Update N/A unrated 1.0.2l-2+deb9u1 03 Nov 2017

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 openssl1.0

Is openssl1.0 safe to use?

Vulert records 13 vulnerabilities for openssl1.0 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 13 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.

How many vulnerabilities does openssl1.0 have?

13 vulnerabilities are recorded for openssl1.0 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 13 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 openssl1.0 vulnerabilities disclosed?

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

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