Geocoder up to 1.6.0 sql.rb within_bounding_box sw_lat/sw_lng/ne_lat/ne_lng sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Geocoder up to 1.6.0. Affected is the function within_bounding_box of the file sql.rb. Executing a manipulation of the argument sw_lat/sw_lng/ne_lat/ne_lng can lead to sql injection.
This vulnerability appears as CVE-2020-7981. The attack may be performed from remote. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability has been found in Geocoder up to 1.6.0 and classified as critical. This vulnerability affects the function within_bounding_box of the file sql.rb. The manipulation of the argument sw_lat/sw_lng/ne_lat/ne_lng with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
sql.rb in Geocoder before 1.6.1 allows Boolean-based SQL injection when within_bounding_box is used in conjunction with untrusted sw_lat, sw_lng, ne_lat, or ne_lng data.
The weakness was presented 01/25/2020. This vulnerability was named CVE-2020-7981 since 01/25/2020. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
Upgrading to version 1.6.1 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Geocoder 1.6.1
Patch: github.com
Timeline
01/25/2020 🔍01/25/2020 🔍
01/26/2020 🔍
03/26/2024 🔍
Sources
Advisory: dcdc3d8675411edce3965941a2ca7c441ca48613Status: Not defined
CVE: CVE-2020-7981 (🔍)
GCVE (CVE): GCVE-0-2020-7981
GCVE (VulDB): GCVE-100-149368
Entry
Created: 01/26/2020 12:57Updated: 03/26/2024 10:43
Changes: 01/26/2020 12:57 (38), 01/26/2020 13:02 (17), 03/26/2024 10:43 (20)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.