CVE-2001-0380 crosscom olicom xlt-f
crosscom olicom xlt-f: no CVSS score yet. EPSS 5.2% estimated probability of exploitation activity in the next 30 days.
Crosscom/Olicom XLT-F running XL 80 IM Version 5.5 Build Level 2 allows a remote attacker SNMP read and write access via a default, undocumented community string 'ILMI'.
- EPSS
- 5.2% (unchanged from 5.2% a week ago; 5.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 93rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://archives.neohapsis.com/archives/bugtraq/2001-03/0364.html
Ask an AI about this CVE
Show the prompt
Explain CVE-2001-0380 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2001-0380?via=ask-ai-copy and https://cve.bz/cve/CVE-2001-0380?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2001-0380 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.