Skip to content

Server side request forgery in gibbon

Critical severity GitHub Reviewed Published Apr 26, 2022 to the GitHub Advisory Database • Updated May 4, 2023

Package

bundler gibbon (RubyGems)

Affected versions

< 3.4.4

Patched versions

3.4.4

Description

Gibbon v3.4.3 and below allows attackers to execute a Server-Side Request Forgery (SSRF) via a crafted URL. This issue has been resolved in version 3.4.4

References

Published by the National Vulnerability Database Apr 25, 2022
Published to the GitHub Advisory Database Apr 26, 2022
Reviewed Apr 27, 2022
Last updated May 4, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.235%
(62nd percentile)

Weaknesses

CVE ID

CVE-2022-27311

GHSA ID

GHSA-vx9g-377x-xwxq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.