Skip to content

Upgrade swagger-parser-v3 to 2.1.17+ to fix CVE-2024-47554 in commons-io#2364

Open
Meenu-Mariya wants to merge 1 commit intolinkedin:mainfrom
Meenu-Mariya:issue-2363
Open

Upgrade swagger-parser-v3 to 2.1.17+ to fix CVE-2024-47554 in commons-io#2364
Meenu-Mariya wants to merge 1 commit intolinkedin:mainfrom
Meenu-Mariya:issue-2363

Conversation

@Meenu-Mariya
Copy link
Copy Markdown

Summary

  1. Why: To resolve issue [Security] Upgrade swagger-parser-v3 to 2.1.17+ to fix CVE-2024-47554 in commons-io #2363 .
  2. What: Upgrade swagger-parser-v3 to 2.1.17+ to fix CVE-2024-47554 in commons-io.

Expected Behavior

The project should use a version of commons-io (2.14.0+) that is not vulnerable to CVE-2024-47554 (Uncontrolled Resource Consumption vulnerability)

Actual Behavior

The project currently uses swagger-parser-v3:2.1.16, which transitively depends on commons-io:2.11.0, a version vulnerable to CVE-2024-47554.

Steps to Reproduce

  1. Run ./gradlew dependencies --configuration runtimeClasspath | grep commons-io
  2. Observe commons-io:2.11.0 is pulled in via swagger-parser-v3:2.1.16
  3. Check CVE database for commons-io:2.11.0 vulnerabilities

Known Workarounds

Upgrade is required to fix the vulnerability.

Additional evidence

  1. CVE-2024-47554: Uncontrolled Resource Consumption in Apache Commons IO
    • Fixed in: commons-io 2.14.0+
  2. Dependency chain: cruise-control → swagger-parser-v3:2.1.16 → commons-io:2.11.0
  3. Solution: swagger-parser-v3:2.1.17+ uses commons-io:2.14.0+
  4. Upgrade: Changed from 2.1.16 to 2.1.22 (latest stable)

Categorization

  • documentation
  • bugfix
  • new feature
  • refactor
  • [x ] security/CVE
  • other

This PR resolves #2363 .

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.

[Security] Upgrade swagger-parser-v3 to 2.1.17+ to fix CVE-2024-47554 in commons-io

1 participant