CVE-2016-2173: Improper Input Validation in Spring AMQP

Summary

13/05/2022
Yes i
Critical
9.8

CVE-2016-2173: Improper Input Validation in Spring AMQP. Affects org.springframework.amqp:spring-amqp versions < 1.5.5. Fixed in 1.5.5. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Spring AMQP is a library that provides support for interacting with the Advanced Message Queuing Protocol (AMQP) in Spring-based applications. It allows developers to send and receive messages asynchronously between applications. This vulnerability affects versions of Spring AMQP before 1.5.5.

Vulnerability Detail

The vulnerability, identified as CVE-2016-2173, is an instance of improper input validation in the DefaultDeserializer class of Spring AMQP. This flaw enables remote attackers to execute arbitrary code on the affected system. By exploiting this vulnerability, an attacker can potentially gain unauthorized access, manipulate data, or disrupt the normal functioning of the application.

How To Fix

Minimum fixed version

1.5.5

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of the library to mitigate the risk of exploitation.

Conclusion

In conclusion, CVE-2016-2173 is a critical vulnerability in Spring AMQP that allows remote code execution. To mitigate this risk, it is crucial to update to version 1.5.5 or later of the library. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for org.springframework.amqp:spring-amqp →

Share this vulnerability

FAQ

Spring AMQP is a library that provides support for interacting with the Advanced Message Queuing Protocol (AMQP) in Spring-based applications. It allows developers to send and receive messages asynchronously between applications.

This vulnerability allows remote attackers to execute arbitrary code on the affected system. This can lead to unauthorized access, data manipulation, or disruption of the application's normal functioning.

To fix this vulnerability, it is recommended to upgrade to version 1.5.5 or later of the Spring AMQP library. This version includes a fix for the input validation issue and ensures that the library is not susceptible to remote code execution attacks.

There is no known workaround for this vulnerability. It is essential to update to the fixed version of the library to mitigate the risk of exploitation.

For more information about this vulnerability, you can refer to the CVE-2016-2173 entry in the National Vulnerability Database (NVD) or the GitHub Advisory Database.

Related vulnerabilities

Recent vulnerabilities recorded for org.springframework.amqp:spring-amqp.

How To Fix

Minimum fixed version

1.5.5

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback