Vulnerability Database · Maven · Package report

org.apache.directory.api:api-asn1-ber: vulnerability history, versions and safety

org.apache.directory.api:api-asn1-ber is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

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.

Vulert verdict on org.apache.directory.api:api-asn1-ber 2.1.9 i

Updated on 23 Oct 2026

Good news: 2.1.9, the version you would install today, has no known vulnerabilities.

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

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

  • Current release 2.1.9 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 19 packages i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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 org.apache.directory.api:api-asn1-ber, 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
2.1.9 29 Sep 2026 none Apache-2.0 — Details →
2.1.8 27 May 2026 none Apache-2.0 — Details →
2.1.7 02 Aug 2024 none Apache-2.0 — Details →
2.1.6 01 Feb 2024 none Apache-2.0 — Details →
2.1.5 08 Oct 2023 none Apache-2.0 — Details →
2.1.4 18 Aug 2023 none Apache-2.0 — Details →
2.1.3 05 Apr 2023 none Apache-2.0 — Details →
2.1.2 10 Aug 2022 none Apache-2.0 — Details →
2.1.1 28 Jul 2022 none Apache-2.0 — Details →
2.1.0 25 Jun 2021 none Apache-2.0 — Details →
2.0.2 22 May 2021 none Apache-2.0 — Details →
2.0.1 21 Mar 2020 none Apache-2.0 — Details →
2.0.0 06 Nov 2019 none Apache-2.0 — Details →
2.0.0.AM4 05 Jun 2019 none Apache-2.0 — Details →
2.0.0.AM3 11 May 2019 none Apache-2.0 — Details →
1.0.3 17 Apr 2019 none Apache-2.0 — Details →
2.0.0.AM2 28 Aug 2018 none Apache-2.0 — Details →
2.0.0.AM1 15 Jul 2018 none Apache-2.0 — Details →
1.0.2 01 Jun 2018 none Apache-2.0 — Details →
1.0.1 30 Apr 2018 none Apache-2.0 — Details →
1.0.0 01 Jun 2017 none Apache-2.0 — Details →
1.0.0-RC2 26 Oct 2016 none Apache-2.0 — Details →
1.0.0-RC1 14 Jun 2016 none Apache-2.0 — Details →
1.0.0-M33 18 Dec 2015 none Apache-2.0 — Details →
1.0.0-M32 14 Oct 2015 none Apache-2.0 — Details →
1.0.0-M31 30 Jun 2015 none Apache-2.0 — Details →
1.0.0-M30 28 Apr 2015 none Apache-2.0 — Details →
1.0.0-M29 29 Mar 2015 none Apache-2.0 — Details →
1.0.0-M28 10 Jan 2015 none Apache-2.0 — Details →
1.0.0-M27 24 Dec 2014 none Apache-2.0 — Details →
1.0.0-M26 19 Nov 2014 none Apache-2.0 — Details →
1.0.0-M25 07 Nov 2014 none Apache-2.0 — Details →
1.0.0-M24 28 Jul 2014 none Apache-2.0 — Details →
1.0.0-M23 29 Jun 2014 none Apache-2.0 — Details →
1.0.0-M22 18 Apr 2014 none Apache-2.0 — Details →
1.0.0-M21 06 Mar 2014 none Apache-2.0 — Details →
1.0.0-M20 14 Aug 2013 none Apache-2.0 — Details →
1.0.0-M19 27 Jun 2013 none Apache-2.0 — Details →
1.0.0-M18 21 Jun 2013 none Apache-2.0 — Details →
1.0.0-M17 29 Apr 2013 none Apache-2.0 — Details →
1.0.0-M16 26 Feb 2013 none Apache-2.0 — Details →
1.0.0-M15 22 Jan 2013 none Apache-2.0 — Details →
1.0.0-M14 21 Dec 2012 none Apache-2.0 — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.directory.api:api-asn1-ber

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 org.apache.directory.api:api-asn1-ber

Is org.apache.directory.api:api-asn1-ber safe to use?

Vulert has no vulnerabilities on record for org.apache.directory.api:api-asn1-ber in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is org.apache.directory.api:api-asn1-ber's Vulert package health score?

Vulert scores org.apache.directory.api:api-asn1-ber 89/100, which reads as healthy. 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 org.apache.directory.api:api-asn1-ber affected?

No. 2.1.9, 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 org.apache.directory.api:api-asn1-ber should I use?

2.1.9 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 org.apache.directory.api:api-asn1-ber have?

0 vulnerabilities are recorded for org.apache.directory.api:api-asn1-ber in the Maven ecosystem: 0 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 org.apache.directory.api:api-asn1-ber vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.directory.api:api-asn1-ber in the last 12 months. 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 org.apache.directory.api:api-asn1-ber 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 org.apache.directory.api:api-asn1-ber for upcoming vulnerabilities?

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