همهٔ گزارش‌ها
زیاد

Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
= 4.29.0
نسخهٔ اصلاح‌شده
4.29.1
نسخه‌های متأثر
>= 5.0.0, <= 5.3.1
نسخهٔ اصلاح‌شده
5.3.2

بهره‌برداری

CVE-2025-32442

احتمال بهره‌برداری در ۳۰ روز آینده: 0.74%

FIRST EPSS · ۱۴۰۵/۰۸/۲۶

شرح آسیب‌پذیری

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

پیوندها

گزارش‌دهندگان

  • Linkster78
  • climba03003
  • mcollina
  • Eomm
  • jsumners