CVE-2002-1360 in the critical feed json
Multiple SSH2 servers and clients do not properly handle strings with null characters in them when the string length is specified by a leng…
published 23y ago modified 4mo ago also EUVD-2002-1344
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.1%
- EPSS 6.1% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
Multiple SSH2 servers and clients do not properly handle strings with null characters in them when the string length is specified by a length field, which could allow remote attackers to cause a denial of service or possibly execute arbitrary code due to interactions with the use of null-terminated strings as implemented using languages such as C, as demonstrated by the SSHredder SSH protocol test suite.
Is CVE-2002-1360 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
6.14% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
archives.neohapsis.com
/archives/vulnwatch/2002-q4/0110.html
mailing-list, vendor-advisory
-
securitytracker.com
/id?1005812
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5797
vdb-entry, signature
-
cert.org
/advisories/CA-2002-36.html
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1005813
vdb-entry
Sources
- CVE List CVE-2002-1360
- NVD CVE-2002-1360
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.