🚨 [security] [php] Update paragonie/sodium_compat 2.1.0 → 2.5.0 (minor)

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ paragonie/sodium_compat (indirect, 2.1.0 → 2.5.0) · Repo

Security Advisories 🚨

🚨 paragonie/sodium_compat affected by vulnerability in libsodium

paragonie/sodium_compat is affected by a vulnerability in libsodium. libsodium before ad3004e, in atypical use cases involving certain custom cryptography or untrusted data to crypto_core_ed25519_is_valid_point, mishandles checks for whether an elliptic curve point is valid because it sometimes allows points that aren't in the main cryptographic group.

Release Notes

2.5.0

Security Fix

Read: A vulnerability in libsodium

This fixes a congruent issue in the main branch of the PHP implementation.

For older PHP versions, see v1.24.0 instead.

2.4.0

The biggest change (besides unit testing) in this release is the optimization of Curve25519 field arithmetic by using object properties instead of an internal array. This skips some internal overhead in PHP (i.e., hash tables and memory allocation) that we ultimately never needed.

Beyond that, we mostly expanded our unit test coverage. We're running Infection to identify code that can be mutated without the test suite failing, and it's identified a lot of false positives but also some useful information. The end result? We've fixed a few bugs.

What's Changed

• Optimize curve25519 field element by removing array by @paragonie-security in #198
• Remove dead or redundant code of Util::(strlen|substr) by @takaram in #201
• Improve Unit Testing Coverage by @paragonie-security in #200
• Bigfixes and Improved Test Coverage by @paragonie-security in #202

New Contributors

• @takaram made their first contribution in #201

Full Changelog: v2.3.1...v2.4.0

2.3.1

Deletes the erroneous PSR-0 autoloader declaration from composer.json, fixing #196

Full Changelog: v2.3.0...v2.3.1

2.3.0

Important

The previous version of sodium_compat was overly permissible with sodium_base642bin() when the *_NO_PADDING variants were specified, which was not compatible with ext-sodium. This has been fixed in v2.3.0.

If you need the old behavior in the meantime, you can call ParagonIE_Core_Base64_Original::decode() or ParagonIE_Core_Base64_UrlSafe:decode() to get lax padding enabled.

Aside from this fix, most of the changes were to the unit test suite in order to improve our mutation testing metrics.

What's Changed

• Fix CI for Fuzz/Mutation Tests by @paragonie-security in #190
• Update .gitattributes for psalm files by @erikn69 in #192
• Fix flaky test for PHP 8.1+ by @paragonie-security in #193
• Test enhancements + base64 no-padding fix by @paragonie-security in #194

New Contributors

• @erikn69 made their first contribution in #192

Full Changelog: v2.2.0...v2.3.0

2.2.0

Version 2.2.0 of Sodium_Compat is mostly a maintenance release. Some dev-dependencies were changed in order to facilitate mutation and fuzz testing in CI. No significant changes to the src directory were required as a result of this additional testing.

What's Changed

• Move namespaced part to composer autoloader by @ywisax in #185
• Test PHP 8.5 in CI on v2.x by @paragonie-security in #188
• Improve Assurance of Sodium_Compat by @paragonie-security in #189

New Contributors

• @ywisax made their first contribution in #185

Full Changelog: v2.1.0...v2.2.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}