Sign inStart freeBook a demo

What is CVE-2023-20015?A medium-severity flaw in Firepower 4100, explained.

Medium severity39 affected products
The short answer

CVE-2023-20015 is a medium-severity flaw (CVSS 6.7) in Firepower 4100 from Cisco, published on 23 February 2023. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.2%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 23 February 2023. Record last updated 7 November 2023. We keep this page's data up to date.

What it does

What is CVE-2023-20015? In plain terms.

An attacker has to be already on the device with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

The official description

A vulnerability in the CLI of Cisco Firepower 4100 Series, Cisco Firepower 9300 Security Appliances, and Cisco UCS 6200, 6300, 6400, and 6500 Series Fabric Interconnects could allow an authenticated, local attacker to inject unauthorized commands. This vulnerability is due to insufficient input validation of commands supplied by the user. An attacker could exploit this vulnerability by authenticating to a device and submitting crafted input to the affected command. A successful exploit could allow the attacker to execute unauthorized commands within the CLI. An attacker with Administrator privileges could also execute arbitrary commands on the underlying operating system of Cisco UCS 6400 and 6500 Series Fabric Interconnects with root-level privileges.

What kind of flaw is it?

  • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CVSS 3.1 scoreMedium · 6.7

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn administrator account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data, change data and take it offline

Severity vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation

Is CVE-2023-20015 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days0.2%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
27out of 100Low

CVE-2023-20015 scores 27. Action: Monitor.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2023-20015 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2023-20015? 39 products.

The published record lists 39 products from 1 vendor. Versions are shown as published: "4.0 to before 4.0(4o)" means from 4.0 up to, but not including, 4.0(4o). If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2023-20015? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

1 link
Precursor Intelligence

Does CVE-2023-20015 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2023-20015 is a medium-severity flaw in Firepower 4100 from Cisco, published on 23 February 2023. An attacker has to be already on the device with an administrator account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

It scores 6.7 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2023-20015 is 27 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching.

For Firepower 4100 from Cisco: version not specified. The record lists 39 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring