| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in ZAPms 1.33/1.40/1.41. This issue affects some unknown processing. Such manipulation of the argument pid leads to sql injection. This vulnerability is referenced as CVE-2013-3050. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability was found in ZAPms 1.33/1.40/1.41. It has been rated as critical. Affected by this issue is an unknown function. The manipulation of the argument pid with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
SQL injection vulnerability in ZAPms 1.41 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter to product.
The weakness was published 04/12/2013 by NoGe (Website). The advisory is shared for download at exploit-db.com. This vulnerability is handled as CVE-2013-3050 since 04/12/2013. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (83313), Exploit-DB (24942), SecurityFocus (BID 58960†), OSVDB (92236†) and Secunia (SA52946†). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/09/2013 🔍04/10/2013 🔍
04/12/2013 🔍
04/12/2013 🔍
04/12/2013 🔍
03/24/2015 🔍
04/10/2025 🔍
Sources
Advisory: 121202Researcher: NoGe
Status: Not defined
CVE: CVE-2013-3050 (🔍)
GCVE (CVE): GCVE-0-2013-3050
GCVE (VulDB): GCVE-100-63980
X-Force: 83313
SecurityFocus: 58960 - ZAPms 'pid' Parameter SQL Injection Vulnerability
Secunia: 52946 - ZAPms "pid" SQL Injection Vulnerability, Moderately Critical
OSVDB: 92236
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2015 15:54Updated: 04/10/2025 21:28
Changes: 03/24/2015 15:54 (55), 02/25/2019 15:04 (5), 01/02/2022 09:28 (3), 04/10/2025 21:28 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.