What is CVE-2022-20966?A medium-severity flaw in Identity Services Engine, explained.
CVE-2022-20966 is a medium-severity flaw (CVSS 5.4) in Identity Services Engine from Cisco, published on 20 January 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 28%. If you run an affected version, plan in the vendor’s fix.
Published 20 January 2023. Record last updated 25 January 2024. We keep this page's data up to date.
What is CVE-2022-20966? In plain terms.
It can be attacked from anywhere on the internet with an ordinary user account, but a person has to take an action first. If it works, the attacker can read some data and change some data.
A vulnerability in the web-based management interface of Cisco Identity Services Engine could allow an authenticated, remote attacker to conduct cross-site scripting attacks against other users of the application web-based management interface. This vulnerability is due to improper validation of input to an application feature before storage within the web-based management interface. An attacker could exploit this vulnerability by creating entries within the application interface that contain malicious HTML or script code. A successful exploit could allow the attacker to store malicious HTML or script code within the application interface for use in further cross-site scripting attacks. Cisco has not yet released software updates that address this vulnerability.
What kind of flaw is it?
- CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan read some data and change some data
Severity vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Is CVE-2022-20966 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 28%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
CVE-2022-20966 scores 36. 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 isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2022-20966 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2022-20966? One product.
The published record lists 1 product from 1 vendor. Versions are shown as published: "before 2.6.0" means every version up to, but not including, 2.6.0. If you run one of these, check your version, then go to the fix below.
- Application
Identity Services Engine
by Cisco
Affected versionsbefore 2.6.02.6.02.6.0-patch12.6.0-patch22.6.0-patch32.6.0-patch52.6.0-patch62.6.0-patch72.6.0-patch82.6.0-patch92.6.0-patch102.6.0-patch112.6.0-patch122.7.0
How do I fix CVE-2022-20966? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- 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.
- 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 linkDoes CVE-2022-20966 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability in the web-based management interface of Cisco Identity Services Engine could allow an authenticated, remote attacker to conduct cross-site s...
- Matched to
- Identity Services Engine on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2022-20966 is a medium-severity flaw in Identity Services Engine from Cisco, published on 20 January 2023. It can be attacked from anywhere on the internet with an ordinary user account, but a person has to take an action first. If it works, the attacker can read some data and change some data.
It scores 5.4 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-20966 is 36 out of 100, which is Low. Its action is "Monitor". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
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 28%. That can change at any time, which is why we keep watching.
For Identity Services Engine from Cisco: before 2.6.0, 2.6.0, 2.6.0-patch1, 2.6.0-patch2, 2.6.0-patch3, 2.6.0-patch5 and 27 more.
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.