LiveActive security incident?Get immediate response
CVE Record

CVE-2021-1312: Cisco Elastic Services Controller Denial of Service Vulnerability

A vulnerability in the system resource management of Cisco Elastic Services Controller (ESC) could allow an unauthenticated, remote attacker to cause a denial of service (DoS) to the health monitor API on an affected device. The vulnerability is due to inadequate provisioning of kernel parameters for the maximum number of TCP connections and SYN backlog. An attacker could exploit this vulnerability by sending a flood of crafted TCP packets to an affected device. A successful exploit could allow the attacker to block TCP listening ports that are used by the health monitor API. This vulnerability only affects customers who use the health monitor API.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-1312 can let a remote unauthenticated attacker disrupt Cisco Elastic Services Controller health monitor API availability. The issue matters mainly where that API is used and reachable. It does not indicate data theft or system takeover in the provided sources.

Executive priority

Treat as a targeted availability risk for organizations relying on Cisco ESC health monitoring. Prioritize if ESC supports production network services or if the health monitor API is broadly reachable.

Technical view

The vulnerability is a resource-management flaw tied to insufficient kernel TCP connection and SYN backlog provisioning. A crafted TCP packet flood can block TCP listening ports used by the Cisco ESC health monitor API. CVSS 3.1 is 5.3, network exploitable, no privileges or user interaction required, with low availability impact only.

Likely exposure

Exposure is limited to Cisco Elastic Services Controller deployments that use the health monitor API, especially if that API is reachable from untrusted or broad networks.

Exploitation context

The source bundle does not show active exploitation, and KEV status is false. Exploitation would affect availability of health monitoring rather than confidentiality or integrity, based on the provided CVSS vector and description.

Researcher notes

Evidence is narrow and vendor-specific. The sources identify Cisco ESC and health monitor API use as the exposure condition, but do not provide version granularity in the supplied bundle. Avoid assuming impact outside ESC or beyond API availability.

Mitigation direction

  • Review Cisco advisory for affected ESC releases and vendor-provided fixed release or configuration guidance.
  • Limit health monitor API reachability to trusted monitoring systems and management networks.
  • Disable or remove health monitor API exposure where it is not operationally required.
  • Monitor ESC availability and health monitor API failures during remediation.

Validation and detection

  • Inventory Cisco ESC deployments and confirm whether the health monitor API is enabled.
  • Check firewall, ACL, and routing paths to identify who can reach the API.
  • Review ESC monitoring logs for unexplained health monitor API availability failures.
  • Validate deployed ESC versions and configuration against Cisco advisory guidance.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-1312 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-1312Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CiscoCisco Elastic Services Controllern/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.