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

CVE-2013-1838 has a CVSS 2.0 base score of 4.0 (Medium). CVSS vector: AV:N/AC:L/Au:S/C:N/I:N/A:P. EPSS exploitation probability: 1.4%.

Is there a patch available for CVE-2013-1838?

Yes, a patch is available for CVE-2013-1838. Update the affected software to the latest version immediately.

Essex CVE-2013-1838

MEDIUM

Resource Management Errors (CWE-399)

2013-03-22 secalert@redhat.com

Denial Of Service Essex Folsom Grizzly Ubuntu Linux

4.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.0 MEDIUM

AV:N/AC:L/Au:S/C:N/I:N/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:S/C:N/I:N/A:P

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Mar 22, 2013 - 21:55 cve.org

MEDIUM 4.0

DescriptionCVE.org

OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) does not properly implement a quota for fixed IPs, which allows remote authenticated users to cause a denial of service (resource exhaustion and failure to spawn new instances) via a large number of calls to the addFixedIp function.

AnalysisAI

OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) does not properly implement a quota for fixed IPs, which allows remote authenticated users to cause a denial of service (resource. Rated medium severity (CVSS 4.0), this vulnerability is remotely exploitable, low attack complexity.

Technical ContextAI

This vulnerability is classified under CWE-399. OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) does not properly implement a quota for fixed IPs, which allows remote authenticated users to cause a denial of service (resource exhaustion and failure to spawn new instances) via a large number of calls to the addFixedIp function. Affected products include: Openstack Essex, Openstack Folsom, Openstack Grizzly, Canonical Ubuntu Linux.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.