{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "versions": [
              {
                "introduced": "1.0.0"
              },
              {
                "fixed": "2.4.16"
              },
              {
                "introduced": "3.0.0"
              },
              {
                "fixed": "3.0.9"
              }
            ]
          },
          "events": [
            {
              "introduced": "8ae9f4fd5a1a90ad912a2aa1dce147f993202655"
            },
            {
              "fixed": "b95c1e83a5075e792292e8e51623b8d888be5b84"
            },
            {
              "introduced": "abdb4c0442df31944d794859724de1899d24963e"
            },
            {
              "fixed": "ff7355c5d81335c3eae17960bbef076ac65b9994"
            }
          ],
          "repo": "https://github.com/spring-projects/spring-amqp",
          "type": "GIT"
        }
      ]
    }
  ],
  "details": "\n\n\n\n\n\n\n\n\n\nIn spring AMQP versions 1.0.0 to\n2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class\nnames were added to Spring AMQP, allowing users to lock down deserialization of\ndata in messages from untrusted sources; however by default, when no allowed\nlist was provided, all classes could be deserialized.\n\n\n\nSpecifically, an application is\nvulnerable if\n\n\n\n\n   *  the\n     SimpleMessageConverter or SerializerMessageConverter is used\n\n   *  the user\n     does not configure allowed list patterns\n\n   *  untrusted\n     message originators gain permissions to write messages to the RabbitMQ\n     broker to send malicious content\n\n\n\n\n\n\n\n\n\n",
  "id": "CVE-2023-34050",
  "modified": "2026-03-13T21:55:02.116719968Z",
  "published": "2023-10-19T08:15:08.357Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://spring.io/security/cve-2023-34050"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}