Ресурсы · 23

Приоритизация уязвимостей и проверка устранения

Связь известных эксплойтов, уязвимых активов, влияния на бизнес и доказательство работоспособности исправления.

Обновлено · 9 min

Вымышленная киберобсерватория с отдельными лотками для уведомлений, инвентаря и доказательств исправления, без людей Редакционная иллюстрация, созданная с помощью ИИ

Чего помогает достичь это руководство

  • Сопоставление оповещений с активами.
  • Оценка фактической срочности.
  • Безопасное развертывание.
  • Проверка и закрытие.

Быстрая проверка

  • Действительно ли затронутый продукт и версия развернуты?
  • Доступен ли актив и является ли он критически важным для бизнеса?
  • Задокументирована ли эксплойтная уязвимость?
  • Что защищает сервис до установки патча?
  • Подтверждает ли проверка, что проблема устранена из актива?

Пошаговый метод

  1. 1

    Консолидация инвентаризации.

    Сопоставление сервисов, продуктов, версий, сред, уязвимостей и владельцев. Одного лишь уведомления о компоненте недостаточно, чтобы доказать, что уязвимый экземпляр развернут.

    Результат: список затронутых активов с указанием даты и неопределенностей.

  2. 2

    Оценка обнаруженных уязвимостей

    Сравните рекомендации поставщика, идентификатор CVE, условия эксплуатации и, где это применимо, каталог известных эксплуатируемых уязвимостей CISA. Запишите, когда был проверен каждый источник.

    Результат: обнаруженные уязвимости с указанием основных источников.

  3. 3

    Установите обоснованный приоритет

    Учитывайте известные способы эксплуатации, доступность ресурсов, необходимые привилегии, обрабатываемые данные, влияние на сервис и доступные способы устранения. Назначьте ответственного и контекстно-зависимый крайний срок.

    Результат: обоснованное решение о приоритете.

  4. 4

    Подготовка изменений

    Сопоставьте зависимости, окно изменений, резервное копирование и откат. Если обновление не может быть применено оперативно, запишите временный контроль и срок его действия.

    Результат: план развертывания и ограниченное исключение.

  5. 5

    Развертывание и тестирование

    Примените исправление или меры по устранению уязвимости от поставщика, используя утвержденный процесс. Проверьте полученную версию, бизнес-процесс и интеграции, которые могут привести к регрессии.

    Результат: запись о развертывании и функциональный результат.

  6. 6

    Проверка закрытия

    Проверьте фактический ресурс подходящим методом, найдите пропущенные экземпляры и повторно просмотрите исключения. Не закрывайте заявку только потому, что обновление было запланировано.

    Результат: подтверждение проверки и обновленный реестр.

Показатели управления

ПоказательЧто он измеряетПервое действие
ОхватКритические активы с известными версиями и владельцамиЗавершение инвентаризации
ЗадержкаВремя от квалификации до подтвержденного исправленияУстранение повторяющихся узких мест
ВерификацияИсправления повторно протестированы на реальных активахВозобновление закрытия без доказательств
ИсключенияОтказы с контролем, владельцем и сроком действияЗакрытие истекших исключений

Распространенные ошибки

  • Ранжирование исключительно по общему показателю без проверки актива
  • Предположение, что наличие KEV означает, что продукт существует в вашей инфраструктуре
  • Развертывание без тестирования поведения сервиса
  • Оставление компенсирующих элементов управления без даты проверки

Часто задаваемые вопросы

Должен ли CVE с наивысшим баллом всегда быть первым?

Показатель описывает техническую серьезность; известная эксплуатация, уязвимость и локальное влияние на сервис определяют порядок действий.

Что делать, если патча нет?

Следуйте мерам защиты поставщика, по возможности уменьшите риски и задокументируйте ответственного, дату проверки и остаточный риск.

Когда работа завершена?

После проверки версии или мер защиты на затронутых экземплярах и тестирования критически важных функций.

Источники: данные, применение и ограничения

Документация проверена .

Подробные справочные заметки в этой версии доступны на английском.

Vulnerability: three complementary viewsCVE · Identify. CVSS · Technical severity. EPSS · Probability. KEV · Known exploitation. Affected version and product. Score from 0.0 to 10.0. 30-day horizon. Official CISA catalogue. Local decision: exposure, impact, evidence and remediation checks.Vulnerability: three complementary viewsCVE · IdentifyAffected version and productCVSS · Technical severityScore from 0.0 to 10.0EPSS · Probability30-day horizonKEV · Known exploitationOfficial CISA catalogueLocal decision: exposure, impact, evidence and remediation checks
Vulnerability: three complementary views
Источники: данные, применение и ограничения
Источник и назначениеПроверенные данные или ориентирКак использоватьСохраняемое ограничение
FIRST · CVSS

Describe technical vulnerability severity using an explicit method and vector.

CVSS 4.0 scores run from 0.0 to 10.0. Base, Threat, Environmental and Supplemental metric groups serve different purposes. Retain the score version, vector and date. Compare it with the installed version, access paths and business consequences before ordering remediation.

Подробнее о методе →

A high score is not evidence of exploitation; a low score does not mean a service has no risk.
FIRST · EPSS

Estimate exploitation probability for a published CVE.

The model looks ahead 30 days. Its score is a probability; its percentile ranks that score relative to other CVEs. Record the data date and distinguish probability from percentile. Add asset exposure and confirmed exploitation evidence.

Подробнее о методе →

The model does not predict harm to your organisation. Low probability does not cancel a critical exposure.
CISA · Known Exploited Vulnerabilities

Identify vulnerabilities listed by CISA as known to be exploited.

The catalogue includes CVE, product, date added and required action. Its official repository also provides the data schema. Check applicability to your products and retain the access date. Review the requested action and vendor advisory before confirming remediation.

Подробнее о методе →

Absence from the catalogue does not establish safety. Administrative deadlines in it are not automatically binding on every organisation.

CVSS, EPSS, KEV и VEX

Подробные справочные заметки в этой версии доступны на английском.

Vulnerability prioritisation: four signals to connect to the asset

A vulnerability queue often mixes information answering different questions. CVSS describes technical severity, EPSS estimates a probability of observed exploitation, KEV records known exploitation and VEX carries a product applicability assertion. A local decision still needs the deployed version, access paths and consequences of exploitation.

These are documentary reference points. EPSS examples, situations and the VEX product are fictional; no current CVE score, real inventory or scan result is presented. This page calculates neither CVSS, organisational risk nor an automatic priority. Proposed evidence and decisions are a local editorial method.

Four distinct signals for a local decision
Four distinct signals for a local decision Four independent panels: CVSS describes severity; EPSS estimates observed exploitation within thirty days; KEV records known exploitation; VEX states declared applicability. Compare them with the deployed product and its context without adding them into one score. CVSS · Severity Metrics and vector Version and author EPSS · Probability Thirty-day horizon Separate date and rank KEV · Known exploitation Product and requested action Catalogue edition VEX · Applicability Issuer, product and time Status and justification Local decision: deployed asset, exposure, consequences, owner and evidence.

Four independent panels: CVSS describes severity; EPSS estimates observed exploitation within thirty days; KEV records known exploitation; VEX states declared applicability. Compare them with the deployed product and its context without adding them into one score.

Four questions and four kinds of information

Four questions and four kinds of information
SourceUseful questionWhat it cannot establish alone
CVSS 4.0What is the technical severity under the assessed metrics?The score proves neither exploitation nor consequences for your service.
EPSSWhat is the estimated probability of observing exploitation of this CVE in the next thirty days?It does not describe compromise of your instance, its controls or business loss.
CISA KEVIs the vulnerability listed as known to be exploited?Listing does not establish that the product exists in your estate; absence does not establish safety.
VEXWhat does an issuer assert about a vulnerability for identified products at a stated time?An assertion alone proves neither deployment of the relevant version nor issuer trustworthiness.

CVSS 4.0: preserve groups, vector and assessment author

A number from 0 to 10 loses meaning when its version, vector and assessed groups disappear. FIRST distinguishes CVSS-B, CVSS-BT, CVSS-BE and CVSS-BTE. Undefined Threat and Environmental metrics take default values rather than disappearing from the calculation.

CVSS 4.0: preserve groups, vector and assessment author
GroupRoleReading check
BaseIntrinsic vulnerability characteristics.A supplier’s CVSS-B is not your priority decision.
ThreatThreat characteristics that can change over time.Date the assessment and explain exploitation information used.
EnvironmentalCharacteristics specific to the consumer’s environment.State the controls and system importance considered rather than silently changing a score.
SupplementalAdditional context, such as Safety or Recovery.These metrics do not modify the final CVSS score; they may inform a separate local analysis.

EPSS: probability, percentile and missing data

FIRST describes a probability from 0 to 1, updated daily, over a thirty-day horizon. The percentile is a relative rank among currently scored vulnerabilities. Do not add probability and percentile or turn their pair into the probability of an attack on your organisation.

EPSS: probability, percentile and missing data
Fictional exampleProvided valuesCorrect reading
A probabilityProbability : 0.05 · Percentile : Unspecified0.05 means a 5% estimated probability of observed exploitation within the model horizon, rather than an estate compromise rate.
Probability and rankProbability : 0.02 · Percentile : 0.97In this fictional example 0.02 means 2%, while 0.97 places the score at the 97th percentile. The rank does not turn a 2% probability into 97%.
No received valueProbability : Unspecified · Percentile : UnspecifiedMissing data remains unknown; it is neither zero nor evidence of no exploitation. Record the failure or the date of the last available value.

Seven useful readings of the KEV schema

The official CISA repository schema describes the catalogue and its entries. The following selection helps retain consultation context rather than enumerate every field. Match each entry to the supplier advisory and actual asset.

Seven useful readings of the KEV schema
FieldsMeaningProposed check
catalogVersion / dateReleasedCatalogue version and publication time.Keep a reference to the consulted edition; distinguish publication time from your assessment time.
cveID / vendorProject / productIdentifier and product associated with the entry.Match name, version, distribution and embedded components before declaring an asset affected.
dateAddedDate the vulnerability entered the catalogue.Do not present it as the first exploitation date or CVE publication date.
requiredActionRequested action to address the vulnerability.Read the complete instruction and supplier references, then document local implementation.
dueDateCatalogue deadline for the requested action.Check the context and scope of the CISA instruction before adopting it as a local deadline.
knownRansomwareCampaignUseKnown indicates confirmed ransomware campaign use; Unknown means CISA lacks confirmation.Do not translate Unknown into never used or a definite false value.
cwesWeakness category codes associated with the entry.Use categories to group causes; they do not replace the CVE identifier or affected version.

Six fictional situations: what is missing before a decision?

High severity, product not located

An advisory reports high severity; the inventory cannot locate that version in the estate.

Confirm presence and version with the owner, including embedded dependencies.

Retain applicability unknown. Absence from an incomplete inventory does not justify closure.

Known exploitation, exposed instance

The vulnerability is listed as known to be exploited and an owner confirms an affected internet-accessible instance.

Review supplier actions and arrange exposure reduction and remediation suited to the service.

Name the owner, interim control and expected verification evidence; a severity score alone supplies none of this traceability.

Low probability, essential service

The fictional EPSS probability is low, but the affected instance supports an essential service.

Assess consequences and access paths before agreeing a change window.

Do not treat a low score as insurance; that instance’s controls are not contextual inputs to EPSS.

VEX for another version

The supplier declares version 2.4.0 not affected; the asset still runs 2.3.0.

Seek an assertion applicable to the installed version and verify its provenance.

Do not extend a conclusion across versions. A VEX document deploys no update.

Temporary control becomes permanent

A temporary rule reduces access; its review date has passed.

Check that it still protects the relevant path, then decide whether to maintain it or apply the fix.

Keep the owner, limits and a new review date. A perimeter control is not automatically an OpenVEX built-in product mitigation.

Patch announced, deployment unverified

A fixed release is available, but the ticket contains only a download link.

Check the version actually deployed, remaining instances and critical functionality.

Close on implementation and verification evidence, rather than the supplier’s availability of a patch.

Eight records for a traceable remediation decision

  • Product, version or build, environment and asset owner.
  • Vulnerability identifier, supplier advisory and relevant exploitation conditions.
  • CVSS version, vector, metric-group nomenclature and assessment author.
  • EPSS date, probability and percentile in separate fields, or an explicit missing value.
  • Dated KEV status, requested action and consulted catalogue edition.
  • Applicable VEX assertion: issuer, product, version, time and any justification.
  • Reasoned local decision, interim control, owner and review date.
  • Deployment or mitigation evidence, verification result and remaining limits.

Read VEX statuses and applicability conditions →

Primary sources and scope

Sources checked on

Подпись и происхождение сборки

Подробные справочные заметки в этой версии доступны на английском.

Verify patch origin and then its application

A fixed version needs connecting to the received package and updated instance. Provenance verification helps establish expected origin; remediation confirmation still requires checking the active version and relevant behaviour.

  • Keep the accepted patch digest and signature/provenance verification results.
  • Match that package to the version actually deployed on each targeted instance.
  • Do not close on authenticity alone: document remediation checks, regressions and remaining limits.

Read the pre-deployment provenance reference →

Sources checked on · SLSA 1.2 · Build: Verifying artifacts · SLSA 1.2 · Build: Provenance · SLSA 1.2 · Build: Track Basics · in-toto · Statement v1 · Sigstore · Verifying Signatures

Обзор каталога CISA KEV

Подробные справочные заметки в этой версии доступны на английском.

KEV is CISA’s catalogue of vulnerabilities known to be exploited. This explorer contains a complete dated snapshot, not a live feed. A CVE or product-name match is a lead to compare with the exact deployed product and version; it does not prove that a visitor’s system is vulnerable or compromised.

Entry names, products, descriptions, required actions and links retain CISA’s language and values. Explanations are editorial. Entries may be added or corrected after this snapshot; consult the official source before an operational decision.

Записи
1769
Различные названия поставщиков/проектов
291
Дата публикации каталога

Counters describe this snapshot only. They do not measure attack counts, vulnerability prevalence or an organisation’s risk. Distinct vendorProject labels are counted exactly as published, without merging aliases or treating them as distinct companies.

Unknown means CISA lacks confirmation of use in a ransomware campaign; it does not mean no exploitation. forensicTriage Yes/No is a separate field described by the schema with a reference to BOD 26-04. An absent field stays unreported. Neither No nor Unknown demonstrates that your asset has not been compromised.

dueDate is the deadline published in the CISA entry for the stated action. It is not a universal SLA, a patch release date or evidence that a patch was installed. The forensicTriage field alone cannot determine your obligations or define an investigation plan. The FedRAMP notice explains how its federal cloud certification programme aligns with BOD 26-04. Check which scope applies before adopting a deadline.

Six readings that prevent a misleading priority

Six readings that prevent a misleading priority
Published fieldUseful readingConclusion to avoid
cveIDJoin sources discussing the same vulnerability.The identifier year does not date KEV inclusion.
vendorProject · productFind the vendor advisory and local inventory.A product name does not replace affected versions and configurations.
dateAddedDate the entry’s inclusion in this catalogue.Do not call it discovery or first-exploitation date.
dueDate · requiredActionRead the published action and deadline together.Do not turn the date into a universal obligation or proof of remediation.
knownRansomwareCampaignUsePreserve Known, Unknown or an absent field.Unknown is not No and does not remove the known exploitation signal underlying KEV.
forensicTriage · cwesSeparate CISA’s indicator from published weakness classes.A CWE is not a specific product or score; No is not a certificate that no incident occurred.

Добавления в каталог по годам

Добавления в каталог по годамEach bar counts entries retained in this snapshot by the year of dateAdded. It is not a discovery year or an exploitation frequency. The first year starts at this snapshot’s earliest entry and the release year is incomplete; these totals are not an annual attack trend.311202155520221872023186202424520252852026
Each bar counts entries retained in this snapshot by the year of dateAdded. It is not a discovery year or an exploitation frequency. The first year starts at this snapshot’s earliest entry and the release year is incomplete; these totals are not an annual attack trend.
Добавления в каталог по годам · dateAdded
Год добавленияЗаписи
2021311
2022555
2023187
2024186
2025245
2026285

Результаты : 311 / 1769 · Страница 8 / 13

Обзор каталога CISA KEV · 2026.11.06
CVEПоставщик или проект · productДата добавления / Срок в записиИспользование в кампаниях вымогателей / forensicTriage
CVE-2020-4006

CWE-78

VMware

Multiple Products

Запись и действие, опубликованные CISA

Multiple VMware Products Command Injection Vulnerability

VMware Workspace One Access, Access Connector, Identity Manager, and Identity Manager Connector contain a command injection vulnerability. An attacker with network access to the administrative configurator on port 8443 and a valid password for the configurator administrator account can execute commands with unrestricted privileges on the underlying operating system.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-4006

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-4427

IBM

Data Risk Manager

Запись и действие, опубликованные CISA

IBM Data Risk Manager Security Bypass Vulnerability

IBM Data Risk Manager contains a security bypass vulnerability that could allow a remote attacker to bypass security restrictions when configured with SAML authentication. By sending a specially crafted HTTP request, an attacker could exploit this vulnerability to bypass the authentication process and gain full administrative access to the system.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-4427

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-4428

CWE-78

IBM

Data Risk Manager

Запись и действие, опубликованные CISA

IBM Data Risk Manager Remote Code Execution Vulnerability

IBM Data Risk Manager contains an unspecified vulnerability which could allow a remote, authenticated attacker to execute commands on the system.�

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-4428

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-4430

CWE-22

IBM

Data Risk Manager

Запись и действие, опубликованные CISA

IBM Data Risk Manager Directory Traversal Vulnerability

IBM Data Risk Manager contains a directory traversal vulnerability that could allow a remote authenticated attacker to traverse directories and send a specially crafted URL request to download arbitrary files from the system.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-4430

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-5735

CWE-121

Amcrest

Cameras and Network Video Recorder (NVR)

Запись и действие, опубликованные CISA

Amcrest Cameras and NVR Stack-based Buffer Overflow Vulnerability

Amcrest cameras and NVR contain a stack-based buffer overflow vulnerability through port 37777 that allows an unauthenticated, remote attacker to crash the device and possibly execute code.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-5735

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-5847

Unraid

Unraid

Запись и действие, опубликованные CISA

Unraid Remote Code Execution Vulnerability

Unraid contains a vulnerability due to the insecure use of the extract PHP function that can be abused to execute remote code as root. This CVE is chainable with CVE-2020-5849 for initial access.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-5847

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-5849

CWE-287, CWE-697

Unraid

Unraid

Запись и действие, опубликованные CISA

Unraid Authentication Bypass Vulnerability

Unraid contains an authentication bypass vulnerability that allows attackers to gain access to the administrative interface. This CVE is chainable with CVE-2020-5847 for remote code execution.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-5849

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-5902

CWE-22

F5

BIG-IP

Запись и действие, опубликованные CISA

F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution Vulnerability

F5 BIG-IP Traffic Management User Interface (TMUI) contains a remote code execution vulnerability in undisclosed pages.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-5902

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2020-6207

CWE-306

SAP

Solution Manager

Запись и действие, опубликованные CISA

SAP Solution Manager Missing Authentication for Critical Function Vulnerability

SAP Solution Manager User Experience Monitoring contains a missing authentication for critical function vulnerability which results in complete compromise of all SMDAgents connected to the Solution Manager.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-6207

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-6287

CWE-306

SAP

NetWeaver

Запись и действие, опубликованные CISA

SAP NetWeaver Missing Authentication for Critical Function Vulnerability

SAP NetWeaver Application Server Java Platforms contains a missing authentication for critical function vulnerability allowing unauthenticated access to execute configuration tasks and create administrative users.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-6287

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-6418

CWE-843

Google

Chromium V8

Запись и действие, опубликованные CISA

Google Chromium V8 Type Confusion Vulnerability

Google Chromium V8 Engine contains a type confusion vulnerability allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-6418

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-6819

CWE-362, CWE-416

Mozilla

Firefox and Thunderbird

Запись и действие, опубликованные CISA

Mozilla Firefox And Thunderbird Use-After-Free Vulnerability

Mozilla Firefox and Thunderbird contain a race condition vulnerability when running the nsDocShell destructor under certain conditions. The race condition creates a use-after-free vulnerability, causing unspecified impacts.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-6819

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-6820

CWE-362

Mozilla

Firefox and Thunderbird

Запись и действие, опубликованные CISA

Mozilla Firefox And Thunderbird Use-After-Free Vulnerability

Mozilla Firefox and Thunderbird contain a race condition vulnerability when handling a ReadableStream under certain conditions. The race condition creates a use-after-free vulnerability, causing unspecified impacts.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-6820

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-7961

CWE-502

Liferay

Liferay Portal

Запись и действие, опубликованные CISA

Liferay Portal Deserialization of Untrusted Data Vulnerability

Liferay Portal contains a deserialization of untrusted data vulnerability that allows remote attackers to execute code via JSON web services.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-7961

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8193

CWE-284

Citrix

Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance

Запись и действие, опубликованные CISA

Citrix ADC, Gateway, and SD-WAN WANOP Appliance Authorization Bypass Vulnerability

Citrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an authorization bypass vulnerability that may allow unauthenticated access to certain URL endpoints. The attacker must have access to the NetScaler IP (NSIP) in order to perform exploitation.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8193

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8195

CWE-20

Citrix

Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance

Запись и действие, опубликованные CISA

Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure Vulnerability

Citrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an information disclosure vulnerability.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8195

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8196

CWE-284

Citrix

Application Delivery Controller (ADC), Gateway, and SD-WAN WANOP Appliance

Запись и действие, опубликованные CISA

Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure Vulnerability

Citrix ADC, Citrix Gateway, and multiple Citrix SD-WAN WANOP appliance models contain an information disclosure vulnerability.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8196

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8243

CWE-94

Ivanti

Pulse Connect Secure

Запись и действие, опубликованные CISA

Ivanti Pulse Connect Secure Code Execution Vulnerability

Ivanti Pulse Connect Secure contains an unspecified vulnerability in the admin web interface that could allow an authenticated attacker to upload a custom template to perform code execution.

requiredAction
Apply updates per vendor instructions.
notes
Reference CISA's ED 21-03 (https://www.cisa.gov/news-events/directives/ed-21-03-mitigate-pulse-connect-secure-product-vulnerabilities) for further guidance and requirements. Note: The due date for addressing this vulnerability aligns with the requirements outlined in ED 21-03. https://nvd.nist.gov/vuln/detail/CVE-2020-8243

www.cisa.gov ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8260

CWE-434

Ivanti

Pulse Connect Secure

Запись и действие, опубликованные CISA

Ivanti Pulse Connect Secure Code Execution Vulnerability

Pulse Connect Secure contains an unspecified vulnerability that allows an authenticated attacker to perform code execution using uncontrolled gzip extraction.

requiredAction
Apply updates per vendor instructions.
notes
Reference CISA's ED 21-03 (https://www.cisa.gov/news-events/directives/ed-21-03-mitigate-pulse-connect-secure-product-vulnerabilities) for further guidance and requirements. Note: The due date for addressing this vulnerability aligns with the requirements outlined in ED 21-03. https://nvd.nist.gov/vuln/detail/CVE-2020-8260

www.cisa.gov ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8467

Trend Micro

Apex One and OfficeScan

Запись и действие, опубликованные CISA

Trend Micro Apex One and OfficeScan Remote Code Execution Vulnerability

Trend Micro Apex One and OfficeScan contain an unspecified vulnerability within a migration tool component that allows for remote code execution.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8467

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8468

CWE-74

Trend Micro

Apex One, OfficeScan and Worry-Free Business Security Agents

Запись и действие, опубликованные CISA

Trend Micro Multiple Products Content Validation Escape Vulnerability

Trend Micro Apex One, OfficeScan, and Worry-Free Business Security agents contain a content validation escape vulnerability that could allow an attacker to manipulate certain agent client components.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8468

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8515

CWE-78

DrayTek

Multiple Vigor Routers

Запись и действие, опубликованные CISA

Multiple DrayTek Vigor Routers Web Management Page Vulnerability

DrayTek Vigor3900, Vigor2960, and Vigor300B routers contain an unspecified vulnerability that allows for remote code execution.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8515

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8599

Trend Micro

Apex One and OfficeScan

Запись и действие, опубликованные CISA

Trend Micro Apex One and OfficeScan Authentication Bypass Vulnerability

Trend Micro Apex One and OfficeScan server contain a vulnerable EXE file that could allow a remote attacker to write data to a path on affected installations and bypass root login.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8599

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8644

CWE-94

PlaySMS

PlaySMS

Запись и действие, опубликованные CISA

PlaySMS Server-Side Template Injection Vulnerability

PlaySMS contains a server-side template injection vulnerability that allows for remote code execution.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8644

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-8655

CWE-269

EyesOfNetwork

EyesOfNetwork

Запись и действие, опубликованные CISA

EyesOfNetwork Improper Privilege Management Vulnerability

EyesOfNetwork contains an improper privilege management vulnerability that may allow a user to run commands as root via a crafted Nmap Scripting Engine (NSE) script to nmap7.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2020-8655

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No

An old identifier can enter the catalogue recently

CVE-2015-5477, associated with ISC BIND in this snapshot, has identifier year 2015 and dateAdded 8 October 2026. These dates answer different questions. The entry calls for following vendor instructions; it does not establish your BIND version, exposure or installation of a fix.

From a public signal to a documented decision

  1. Qualify the match

    Keep the CVE, source and date, then establish product, version, embedded component and exposure. An SBOM may locate a component without proving its runtime condition.

  2. Read the action at its source

    Open the vendor advisory and updates. Separate updating, mitigation, discontinuing a product and searching for compromise evidence; a patch does not replace these other decisions.

  3. Document the change

    Assign an owner, prepare rollback and verify dependencies. A mitigation remains a scoped measure with an explicit validity period.

  4. Verify the resulting state

    Retain an observed version, checked configuration and service test. Closing a task needs evidence concerning the actual asset, beyond a console status.

Source release : · Documentary review :

CISA KEV data reused under CC0 1.0. Reuse implies no CISA affiliation or endorsement and grants no right to use the CISA logo or DHS seal.

Документальные сведения · CISA KEV

How we publish this official snapshot

Подробные справочные заметки в этой версии доступны на английском.

The copy is identified by its catalogue version, dateReleased, official mirror commit and source-file digest. CISA publication, GitHub synchronisation and our review are distinct events. Aggregates are computed from the retained entries; no visitor inventory collection or vulnerability scan takes place.

catalogVersion
2026.11.06
dateReleased
GitHub commit
e5b3a9b25050a8da26c96266c5bfe438ee0bdebc ·
SHA-256
47e0406b2be5a40420eff66f3d90e83eb8883dae6ff4d08e1b2a942c366f6cc2

Counters describe this snapshot only. They do not measure attack counts, vulnerability prevalence or an organisation’s risk. Distinct vendorProject labels are counted exactly as published, without merging aliases or treating them as distinct companies.

Каталог и метод →

Source release : · Documentary review :

CISA KEV data reused under CC0 1.0. Reuse implies no CISA affiliation or endorsement and grants no right to use the CISA logo or DHS seal.

Официальные ссылки

Ссылки подтверждают метод. Адаптируйте проверки к вашему контексту; они не являются сертификацией. Оригинальные названия ссылок и исходные документы могут быть на другом языке.

Источники проверены .