| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in web-cyradm. Affected by this issue is some unknown functionality of the file search.php. Performing a manipulation of the argument searchstring results in sql injection. This vulnerability is cataloged as CVE-2007-10001. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability classified as problematic has been found in web-cyradm (affected version unknown). This affects an unknown functionality of the file search.php. The manipulation of the argument searchstring with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality.
The weakness was shared 01/05/2023 as 3e8f0717f133907bb6a09cb674b05c5f273da3e1. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2007-10001. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:search.php it is possible to find vulnerable targets with Google Hacking.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The advisory contains the following remark:
Fixed information disclosure by SQL injection
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 3.5
CNA Vector (VulDB): 🔍
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
Google Hack: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
01/05/2023 🔍01/05/2023 🔍
01/05/2023 🔍
01/28/2023 🔍
Sources
Product: github.comAdvisory: 3e8f0717f133907bb6a09cb674b05c5f273da3e1
Status: Confirmed
CVE: CVE-2007-10001 (🔍)
GCVE (CVE): GCVE-0-2007-10001
GCVE (VulDB): GCVE-100-217449
Entry
Created: 01/05/2023 12:31Updated: 01/28/2023 15:47
Changes: 01/05/2023 12:31 (40), 01/28/2023 15:41 (2), 01/28/2023 15:47 (28)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.