Skip to content

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

Merged
meyfa merged 1 commit intomainfrom
renovate/npm-fastify-vulnerability
Apr 18, 2025
Merged

fix(deps): update dependency fastify to v5.3.2 [security]#218
meyfa merged 1 commit intomainfrom
renovate/npm-fastify-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
fastify (source) 5.3.1 -> 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.

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


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 renovate bot requested a review from a team as a code owner April 18, 2025 18:53
@renovate renovate bot changed the title fix(deps): update dependency fastify to v5.3.1 [security] fix(deps): update dependency fastify to v5.3.2 [security] Apr 18, 2025
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 2 times, most recently from 25cd23a to de24c8e Compare April 18, 2025 21:37
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from de24c8e to 4fd3413 Compare April 18, 2025 21:51
@meyfa meyfa enabled auto-merge (squash) April 18, 2025 21:52
@meyfa meyfa merged commit 51c635f into main Apr 18, 2025
4 checks passed
@meyfa meyfa deleted the renovate/npm-fastify-vulnerability branch April 18, 2025 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant