What is the CVSS score of CVE-2013-3441?

CVE-2013-3441 has a CVSS 2.0 base score of 5.4 (Medium). CVSS vector: AV:N/AC:H/Au:N/C:N/I:N/A:C. EPSS exploitation probability: 0.7%.

Aironet 3600 CVE-2013-3441

MEDIUM

Buffer Overflow (CWE-119)

2013-07-23 psirt@cisco.com

Buffer Overflow Denial Of Service Cisco Aironet 3600 Aironet 3600E Aironet 3600I Aironet 3600P

5.4

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

AV:N/AC:H/Au:N/C:N/I:N/A:C

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:N/C:N/I:N/A:C

Attack Vector

Network

Attack Complexity

High

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Jul 23, 2013 - 11:03 cve.org

MEDIUM 5.4

DescriptionCVE.org

Cisco Aironet 3600 access points allow remote attackers to cause a denial of service (memory corruption and device crash) by disrupting Cisco Wireless LAN Controller communication and consequently forcing many transitions from FlexConnect mode to Standalone mode, aka Bug ID CSCuh71210.

AnalysisAI

Cisco Aironet 3600 access points allow remote attackers to cause a denial of service (memory corruption and device crash) by disrupting Cisco Wireless LAN Controller communication and consequently. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Cisco Aironet 3600 access points allow remote attackers to cause a denial of service (memory corruption and device crash) by disrupting Cisco Wireless LAN Controller communication and consequently forcing many transitions from FlexConnect mode to Standalone mode, aka Bug ID CSCuh71210. Affected products include: Cisco Aironet 3600, Cisco Aironet 3600E, Cisco Aironet 3600I, Cisco Aironet 3600P.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.