graphql-fastify-server icon indicating copy to clipboard operation
graphql-fastify-server copied to clipboard

Published 20 hours ago • verified publisher icon rpvsilva

fix(deps): update dependency fastify to v5.3.2 [security]

Open renovate[bot] opened this issue 7 months ago • 0 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
fastify (source) 5.1.0 -> 5.3.2 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-32442

Impact

In applications that specify different validation strategies for different content types, it's possible to bypass the validation by providing a slightly altered content type such as with different casing or altered whitespacing before ;.

Users using the the following pattern are affected:

fastify.post('/', {
  handler(request, reply) {
    reply.code(200).send(request.body)
  },
  schema: {
    body: {
      content: {
        'application/json': {
          schema: {
            type: 'object',
            properties: {
              'foo': {
                type: 'string',
              }
            },
            required: ['foo']
          }
        },
      }
    }
  }
})

User using the following pattern are not affected:

fastify.post('/', {
  handler(request, reply) {
    reply.code(200).send(request.body)
  },
  schema: {
    body: {
      type: 'object',
      properties: {
        'foo': {
          type: 'string',
        }
      },
      required: ['foo']
    }
  }
})

Patches

This was patched in v5.3.1, but unfortunately it did not cover all problems. This has been fully patched in v5.3.2. Version v4.9.0 was also affected by this issue. This has been fully patched in v4.9.1.

Workarounds

Do not specify multiple content types in the schema.

References

Are there any links users can visit to find out more?

https://hackerone.com/reports/3087928

Release Notes

fastify/fastify (fastify)

v5.3.2

Compare Source

⚠️ Security Release ⚠️

Unfortunately, v5.3.1 did not include a complete fix for "Invalid content-type parsing could lead to validation bypass" and CVE-2025-32442. This is a follow-up patch to cover an edge case.

What's Changed
New Contributors

Full Changelog: https://github.com/fastify/fastify/compare/v5.3.1...v5.3.2

v5.3.1

Compare Source

⚠️ Security Release ⚠️

What's Changed

New Contributors

Full Changelog: https://github.com/fastify/fastify/compare/v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/fastify/fastify/compare/v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/fastify/fastify/compare/v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/fastify/fastify/compare/v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/fastify/fastify/compare/v5.1.0...v5.2.0

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • [ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] avatar Apr 18 '25 15:04 renovate[bot]