VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

pjproject: vulnerability history, versions and safety

pjproject is a package in the Alpine ecosystem. Vulert records 36 vulnerabilities for it across 31 releases, from Dec 2021 to Apr 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded U36
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 pjproject vulnerabilities

Vulert verdict on pjproject i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 36 vulnerabilities on record across 1 year, 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 36 over 1 year · 0 in the last year i
  • Latest disclosure 25 Apr 2022 i
  • Highest CVSS 9.8 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 pjproject, 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 31 of 31 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 6
  • 2022 30

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

03 Vulnerabilities

Recorded vulnerabilities for pjproject

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in PJSIP Package: Potential Dialog Set Collision 9.8 critical 2.12-r0 22 Feb 2022
Critical Stack-Buffer Overflow in PJSIP Package - CVE-2022-24754 9.8 critical 2.12.1-r0 11 Mar 2022
Critical Vulnerability in PJSIP: RTCP Feedback RPSI Packet Parsing Issue 9.8 critical 2.12.1-r0 06 Apr 2022
Critical Integer Underflow Vulnerability in PJSIP Package 9.8 critical 2.12-r0 22 Dec 2021
Multiple UAC Dialogs Hash Key Premature Freeing Vulnerability in pjproject 9.8 critical 2.12-r0 22 Feb 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 pjproject

Is pjproject safe to use?

Vulert records 36 vulnerabilities for pjproject in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 36 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 pjproject have?

36 vulnerabilities are recorded for pjproject in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 36 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 pjproject vulnerabilities disclosed?

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

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