CVE-2008-4052 json
Stack-based buffer overflow in SMGSHR.EXE in OpenVMS for Integrity Servers 8.2-1, 8.3, and 8.3-1H1 and OpenVMS ALPHA 7.3-2, 8.2, and 8.3 al…
published 2008-09-11 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4037
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in SMGSHR.EXE in OpenVMS for Integrity Servers 8.2-1, 8.3, and 8.3-1H1 and OpenVMS ALPHA 7.3-2, 8.2, and 8.3 allows local users to cause a denial of service (crash) or gain privileges via unspecified vectors.
Patch / fix
- mail.openvms.org/Lists/alerts/Message/837.html patch
- mail.openvms.org/Lists/alerts/Message/834.html patch
- mail.openvms.org/Lists/alerts/Message/835.html patch
- mail.openvms.org/Lists/alerts/Message/833.html patch
- mail.openvms.org/Lists/alerts/Message/836.html patch
- mail.openvms.org/Lists/alerts/Message/832.html patch
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
mail.openvms.org
/Lists/alerts/Message/837.html
mailing-list, patch
-
mail.openvms.org
/Lists/alerts/Message/834.html
mailing-list, patch
-
mail.openvms.org
/Lists/alerts/Message/835.html
mailing-list, patch
-
mail.openvms.org
/Lists/alerts/Message/833.html
mailing-list, patch
-
mail.openvms.org
/Lists/alerts/Message/836.html
mailing-list, patch
-
mail.openvms.org
/Lists/alerts/Message/832.html
mailing-list, patch
-
secunia.com
/advisories/31581
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44664
vdb-entry
-
vupen.com
/english/advisories/2008/2439
vdb-entry
Sources
- CVE List CVE-2008-4052
- NVD CVE-2008-4052
Fencer Vulns 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.