Skip to content

chore(deps): update dependency webrick to v1.8.2 [security]#137

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rubygems-webrick-vulnerability
Open

chore(deps): update dependency webrick to v1.8.2 [security]#137
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rubygems-webrick-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 24, 2024

This PR contains the following updates:

Package Change Age Confidence
webrick 1.7.01.8.2 age confidence

HTTP Request Smuggling in ruby webrick

CVE-2024-47220 / GHSA-6f62-3596-g6w7

More information

Details

An issue was discovered in the WEBrick toolkit through 1.8.1 for Ruby. It allows HTTP request smuggling by providing both a Content-Length header and a Transfer-Encoding header, e.g., "GET /admin HTTP/1.1\r\n" inside of a "POST /user HTTP/1.1\r\n" request. NOTE: the supplier's position is "Webrick should not be used in production."

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Ruby WEBrick read_headers method can lead to HTTP Request/Response Smuggling

CVE-2025-6442 / GHSA-r995-q44h-hr64

More information

Details

Ruby WEBrick read_header HTTP Request Smuggling Vulnerability. This vulnerability allows remote attackers to smuggle arbitrary HTTP requests on affected installations of Ruby WEBrick. This issue is exploitable when the product is deployed behind an HTTP proxy that fulfills specific conditions.

The specific flaw exists within the read_headers method. The issue results from the inconsistent parsing of terminators of HTTP headers. An attacker can leverage this vulnerability to smuggle arbitrary HTTP requests. Was ZDI-CAN-21876.

Severity

  • CVSS Score: 6.5 / 10 (Medium)
  • Vector String: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

ruby/webrick (webrick)

v1.8.2

Compare Source

What's Changed

New Contributors

Full Changelog: ruby/webrick@v1.8.1...v1.8.2

v1.8.1

Compare Source

What's Changed

Full Changelog: ruby/webrick@v1.8.0...v1.8.1

v1.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: ruby/webrick@v1.7.0...v1.8.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • 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 force-pushed the renovate/rubygems-webrick-vulnerability branch from 7a61b45 to fe17e40 Compare August 10, 2025 12:55
@renovate renovate Bot force-pushed the renovate/rubygems-webrick-vulnerability branch from fe17e40 to bd87475 Compare December 31, 2025 13:47
@renovate renovate Bot changed the title chore(deps): update dependency webrick to v1.8.2 [security] chore(deps): update dependency webrick to v1.8.2 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/rubygems-webrick-vulnerability branch March 27, 2026 01:16
@renovate renovate Bot changed the title chore(deps): update dependency webrick to v1.8.2 [security] - autoclosed chore(deps): update dependency webrick to v1.8.2 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/rubygems-webrick-vulnerability branch 2 times, most recently from bd87475 to 87b15f5 Compare March 30, 2026 21:53
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.

0 participants