CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
Multiple stack-based buffer overflows in ovalarmsrv in HP OpenView Network Node Manager (OV NNM) 7.51, and possibly 7.01, 7.50, and 7.53, allow remote attackers to execute arbitrary code via a long (1) REQUEST_SEV_CHANGE (aka number 47), (2) REQUEST_SAVE_STATE (aka number 61), or (3) REQUEST_RESTORE_STATE (aka number 62) request to TCP port 2954.
Improper Restriction of Operations within the Bounds of a Memory Buffer The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
9
AV:N/AC:L/Au:N/C:P/I:P/A:C
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
28.33%
–
–
2022-04-03
–
–
28.33%
–
–
2023-03-12
–
–
–
44.72%
–
2023-04-16
–
–
–
41.36%
–
2023-05-28
–
–
–
37.06%
–
2023-09-24
–
–
–
43.94%
–
2024-01-07
–
–
–
44.72%
–
2024-03-24
–
–
–
40.57%
–
2024-06-02
–
–
–
40.57%
–
2024-12-22
–
–
–
51.77%
–
2025-01-19
–
–
–
51.77%
–
2025-03-18
–
–
–
–
40.91%
2025-03-18
–
–
–
–
40.91,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Publication date : 2008-04-06 22h00 +00:00 Author : Luigi Auriemma EDB Verified : Yes
#######################################################################
Luigi Auriemma
Application: HP OpenView Network Node Manager
http://www.openview.hp.com/products/nnm/
Versions: <= 7.53
Platforms: Windows (tested), Solaris, Linux, HP-UX
Bugs: A] format string in ovalarmsrv
B] multiple buffer-overflows in ovalarmsrv
C] Denial of Service in ovalarmsrv
Exploitation: remote
Date: 07 Apr 2008
Author: Luigi Auriemma
e-mail: aluigi@autistici.org
web: aluigi.org
#######################################################################
1) Introduction
2) Bugs
3) The Code
4) Fix
#######################################################################
===============
1) Introduction
===============
>From vendor's website:
OpenView NNM "automates the process of developing a hyper-accurate
topology of your physical network, virtual network services and the
complex relationships between them. It then uses that topology as the
basis for intelligent root cause analysis to enhance network
availability and performance."
#######################################################################
=======
2) Bugs
=======
------------------------------
A] format string in ovalarmsrv
------------------------------
The ovalarmsrv.exe process listening on port 2953 is affected by a
format string vulnerability caused by the calling of ov.fprintf_new
(which then calls vsprintf) using the final message without a format
argument:
"Connection Refused; Data in listener port corrupt: ATTACKER_STRING"
------------------------------------------
B] multiple buffer-overflows in ovalarmsrv
------------------------------------------
The same process listens also on port 2954 where are handled some types
of requests using specific sscanf formats:
REQUEST_SEV_CHANGE (47): "%d %d %d %[^\n]"
REQUEST_SAVE_STATE (61): "%d %[^\n]s"
REQUEST_LOCAL (66): "%d"
REQUEST_RESTORE_STATE (62): "%d %s"
REQUEST_SAVE_DIR (63):
As visible by the previous format arguments there are no checks on the
length of the client string handled by the requests 47, 61 and 62 which
can be used to exploit a stack based buffer-overflow vulnerability
using a string parameter longer than 512 bytes.
----------------------------------
C] Denial of Service in ovalarmsrv
----------------------------------
Another problem of the ovalarmsrv service is that it can be easily
freezed with CPU at 100% and without the possibility of handling
further requests on port 2953/2954 simply sending some invalid values.
#######################################################################
===========
3) The Code
===========
A]
echo %n%n%s%n%n%s | nc SERVER 2953 -v -v
B]
echo 62 AAAAAAAAAAAAA...512_'A's...AAAAAAAAAAAAA | nc SERVER 2954 -v -v
C]
echo 47 1 2 what_you_want | nc SERVER 2954 -v -v -w 1
#######################################################################
======
4) Fix
======
No fix
#######################################################################
# milw0rm.com [2008-04-07]