CVE-2009-0629 json
The (1) Airline Product Set (aka ALPS), (2) Serial Tunnel Code (aka STUN), (3) Block Serial Tunnel Code (aka BSTUN), (4) Native Client Inte…
published 17y ago modified 4mo ago also EUVD-2009-0632
- cvss
- 5.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
The (1) Airline Product Set (aka ALPS), (2) Serial Tunnel Code (aka STUN), (3) Block Serial Tunnel Code (aka BSTUN), (4) Native Client Interface Architecture (NCIA) support, (5) Data-link switching (aka DLSw), (6) Remote Source-Route Bridging (RSRB), (7) Point to Point Tunneling Protocol (PPTP), (8) X.25 for Record Boundary Preservation (RBP), (9) X.25 over TCP (XOT), and (10) X.25 Routing features in Cisco IOS 12.2 and 12.4 allows remote attackers to cause a denial of service (device reload) via a series of crafted TCP packets.
Is CVE-2009-0629 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
4.03% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.4 | AV:N/AC:H/Au:N/C:N/I:N/A:C |
Classification
- Technology feeds
References
-
cisco.com
/en/US/products/products_security_advisory09186a0080a904cb.shtml
vendor-advisory
-
cisco.com
/en/US/products/products_security_advisory09186a0080a90469.shtml
vendor-advisory
-
securitytracker.com
/id?1021903
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49420
vdb-entry, third-party-advisory
-
secunia.com
/advisories/34438
third-party-advisory
-
securityfocus.com
/bid/34238
vdb-entry, third-party-advisory
-
vupen.com
/english/advisories/2009/0851
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2009-0629
- NVD CVE-2009-0629
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.