CVE-2012-5520 json
The send_to_sourcefire function in manage_sql.c in OpenVAS Manager 3.x before 3.0.4 allows remote attackers to execute arbitrary commands v…
published 2012-11-26 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5412
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
The send_to_sourcefire function in manage_sql.c in OpenVAS Manager 3.x before 3.0.4 allows remote attackers to execute arbitrary commands via the (1) IP address or (2) port number field in an OMP request.
Patch / fix
- openvas.org/OVSA20121112.html advisory
Exploit prediction
3.05% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- openvas.org http://www.openvas.org/OVSA20121112.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
openvas.org
/OVSA20121112.html
exploit, patch, vendor-advisory
-
archives.neohapsis.com
/archives/bugtraq/2012-11/0059.html
mailing-list
-
archives.neohapsis.com
/archives/bugtraq/2012-11/0047.html
mailing-list
-
openwall.com
/lists/oss-security/2012/11/13/9
mailing-list
-
openwall.com
/lists/oss-security/2012/11/14/5
mailing-list
-
secunia.com
/advisories/49128
third-party-advisory
- wald.intevation.org /scm/viewvc.php?view=rev&root=openvas&revision=14437
-
securityfocus.com
/bid/56497
vdb-entry
-
openwall.com
/lists/oss-security/2012/11/14/11
mailing-list
-
archives.neohapsis.com
/archives/bugtraq/2012-11/0055.html
mailing-list
-
openwall.com
/lists/oss-security/2012/11/13/12
mailing-list
Sources
- CVE List CVE-2012-5520
- NVD CVE-2012-5520
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.