pear/crypt_gpg vulnerabilities

Provides an object oriented interface to the GNU Privacy Guard (GnuPG). It requires the GnuPG executable to be on the system.

Registry
Composer
Latest
2.0.0
License
LGPL-2.1

1 known advisory

The latest version, 2.0.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require pear/crypt_gpg:^2.0.0

Is your project on an affected pear/crypt_gpg?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for pear/crypt_gpg

  • MediumCVE-2022-24953GHSA-59x4-67mh-px5418 Feb 2022

    Crypt_GPG does not prevent additional options in GPG calls

    Affected
    <1.6.7
    Fixed in
    1.6.7

Is your pear/crypt_gpg version vulnerable?

Which of your client projects still run an old pear/crypt_gpg?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.