Resurssit · 23

Haavoittuvuuksien priorisointi ja korjaavien toimenpiteiden varmentaminen

Yhdistää tunnetut hyväksikäyttömahdollisuudet, altistuneet resurssit, liiketoimintavaikutukset ja toimivan korjauksen todisteet.

Päivitetty · 9 min

Kuvitteellinen kyberobservatorio, jossa tiedotteet, laiteluettelo ja korjaustodisteet ovat eri alustoilla, ilman ihmisiä Tekoälyllä luotu toimituksellinen kuvitus

Mitä tämä opas auttaa saavuttamaan

  • Yhdistä hälytykset resursseihin
  • Luokittele todellinen kiireellisyys
  • Ota käyttöön turvallisesti
  • Tarkista ja sulje

Pikatarkistus

  • Onko kyseinen tuote ja versio todella otettu käyttöön?
  • Onko resurssi saavutettavissa ja liiketoimintakriittinen?
  • Onko hyväksikäyttö dokumentoitu?
  • Mikä suojaa palvelua ennen korjausta?
  • Vahvistaako tarkistus, että ongelma on poistunut resurssista?

Vaiheittainen menetelmä

  1. 1

    Yhdistä luettelo

    Kartoita palvelut, tuotteet, versiot, ympäristöt, altistuminen ja omistajat. Pelkkä komponenttitiedote ei todista, että haavoittuva instanssi on otettu käyttöön.

    Toimitettava: päivätty luettelo kyseisistä resursseista ja epävarmuustekijät.

  2. 2

    Määrittele löydös

    Vertaa toimittajatiedotetta, CVE-tunnistetta, hyväksikäyttöehtoja ja tarvittaessa CISA:n luetteloa tunnetuista hyödynnetyistä haavoittuvuuksista. Kirjaa ylös, milloin kukin lähde on tarkistettu.

    Toimitettava: ensisijaisten viitteiden löytäminen.

  3. 3

    Aseta puolustettava prioriteetti.

    Ota huomioon tunnettu hyväksikäyttö, resurssin saavutettavuus, tarvittavat oikeudet, käsiteltävät tiedot, palvelun vaikutus ja käytettävissä olevat korjaavat toimenpiteet. Määritä omistaja ja kontekstikohtainen määräaika.

    Toimitettava: perusteltu prioriteettipäätös.

  4. 4

    Valmistele muutos.

    Kartoita riippuvuudet, muutosikkuna, varmuuskopiointi ja palautus. Jos päivitystä ei voida ottaa käyttöön nopeasti, kirjaa väliaikainen hallinta ja sen voimassaoloaika.

    Toimitettava: käyttöönottosuunnitelma ja rajoitettu poikkeus.

  5. 5

    Käyttöönotto ja testaus.

    Käytä toimittajan korjausta tai lievennystä hyväksytyn prosessin mukaisesti. Tarkista tuloksena oleva versio, liiketoimintaprosessi ja integraatiot, jotka saattavat taantua.

    Toimitettava: käyttöönottotietue ja toiminnallinen tulos.

  6. 6

    Varmista sulkeminen.

    Tarkista todellinen resurssi sopivalla menetelmällä, etsi puuttuvia esiintymiä ja tarkastele poikkeuksia uudelleen. Älä sulje tukipyyntöä, koska päivitys oli vain ajoitettu.

    Toimitettava: varmennustodisteet ja päivitetty rekisteri.

Johdon indikaattorit

IndikaattoriMitä se mittaaEnsimmäinen toimenpide
KattavuusKriittiset resurssit, joilla on tunnetut versiot ja omistajatTäydennä luettelo
ViivästysAika hyväksynnästä varmennettuun korjaukseenPoista toistuvat pullonkaulat
VarmennusKorjaukset testattu uudelleen reaaliresursseillaAvaa sulkemiset uudelleen ilman todisteita
PoikkeuksetVapautukset, joihin liittyy hallinta, omistaja ja vanheneminenSulje vanhentuneet poikkeukset

Yleisiä virheitä

  • Sijoitus pelkästään yleisen pistemäärän perusteella ilman resurssin tarkistamista
  • Olettaen, että KEV-listaus tarkoittaa, että tuote on olemassa omaisuudessasi
  • Käyttöönotto ilman palvelun toiminnan testaamista
  • Kompensoivien kontrollien jättäminen ilman tarkistuspäivämäärää

Usein kysytyt kysymykset

Onko korkeimman pistemäärän saanut CVE aina mentävä ensin?

Pistemäärä kuvaa teknistä vakavuutta; tunnettu hyväksikäyttö, altistuminen ja paikallisen palvelun vaikutus ohjaavat toimintajärjestystäsi.

Entä jos korjausta ei ole olemassa?

Noudata toimittajan lieventäviä toimenpiteitä, vähennä altistumista mahdollisuuksien mukaan ja dokumentoi omistaja, tarkistuspäivämäärä ja jäännösriski.

Milloin työ päättyy?

Kun versio tai lieventävä toimenpide on varmistettu kyseisissä tapauksissa ja kriittinen toiminnallisuus on testattu.

Lähteet: tiedot, käyttö ja rajat

Aineisto tarkistettu .

Tämän kieliversion tarkemmat lähdekuvaukset ovat englanniksi.

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
Lähteet: tiedot, käyttö ja rajat
Lähde ja tarkoitusTarkistettu tieto tai vertailukohtaKäyttö käytännössäHuomioitava rajoitus
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.

Tutustu menetelmään →

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.

Tutustu menetelmään →

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.

Tutustu menetelmään →

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

CVSS, EPSS, KEV ja VEX

Tämän kieliversion tarkemmat lähdekuvaukset ovat englanniksi.

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

Koosteen allekirjoitus ja alkuperä

Tämän kieliversion tarkemmat lähdekuvaukset ovat englanniksi.

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

Tutki CISAn KEV-luetteloa

Tämän kieliversion tarkemmat lähdekuvaukset ovat englanniksi.

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.

Tietueet
1769
Erilliset toimittaja-/projektinimikkeet
291
Luettelon julkaisuaika

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.

Luetteloon lisäykset vuosittain

Luetteloon lisäykset vuosittainEach 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.
Luetteloon lisäykset vuosittain · dateAdded
LisäysvuosiTietueet
2021311
2022555
2023187
2024186
2025245
2026285

Tulokset : 311 / 1769 · Sivu 3 / 13

Tutki CISAn KEV-luetteloa · 2026.11.06
CVEToimittaja tai projekti · productLisäyspäivä / Tietueen määräpäiväKäyttö kiristyshaittaohjelmakampanjoissa / forensicTriage
CVE-2017-9805

CWE-502

Apache

Struts

CISAn julkaisema tietue ja toimenpide

Apache Struts Deserialization of Untrusted Data Vulnerability

Apache Struts REST Plugin uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to remote code execution when deserializing XML payloads.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2017-9822

CWE-20

DotNetNuke (DNN)

DotNetNuke (DNN)

CISAn julkaisema tietue ja toimenpide

DotNetNuke (DNN) Remote Code Execution Vulnerability

DotNetNuke (DNN) contains a vulnerability that may allow for remote code execution via cookie deserialization.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-0171

CWE-20

Cisco

IOS and IOS XE

CISAn julkaisema tietue ja toimenpide

Cisco IOS and IOS XE Software Smart Install Remote Code Execution Vulnerability

Cisco IOS and IOS XE Software improperly validates packet data, allowing an unauthenticated, remote attacker to trigger a reload of an affected device, cause a denial-of-service (DoS) condition, or perform code execution on the affected device.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-0296

CWE-20

Cisco

Adaptive Security Appliance (ASA)

CISAn julkaisema tietue ja toimenpide

Cisco Adaptive Security Appliance (ASA) Denial-of-Service Vulnerability

Cisco Adaptive Security Appliance (ASA) contains an improper input validation vulnerability with HTTP URLs. Exploitation could allow an attacker to cause a denial-of-service (DoS) condition or information disclosure.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-0798

CWE-787

Microsoft

Office

CISAn julkaisema tietue ja toimenpide

Microsoft Office Memory Corruption Vulnerability

Microsoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0802.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-0802

CWE-787

Microsoft

Office

CISAn julkaisema tietue ja toimenpide

Microsoft Office Memory Corruption Vulnerability

Microsoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0798.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-11776

CWE-20

Apache

Struts

CISAn julkaisema tietue ja toimenpide

Apache Struts Remote Code Execution Vulnerability

Apache Struts contains a vulnerability that allows for remote code execution under two circumstances. One, where the alwaysSelectFullNamespace option is true and the value isn't set for a result defined in underlying configurations and in same time, its upper package configuration have no or wildcard namespace. Or, using URL tag which doesn't have value and action set and in same time, its upper package configuration have no or wildcard namespace.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-13379

CWE-22

Fortinet

FortiOS

CISAn julkaisema tietue ja toimenpide

Fortinet FortiOS SSL VPN Path Traversal Vulnerability

Fortinet FortiOS SSL VPN web portal contains a path traversal vulnerability that may allow an unauthenticated attacker to download FortiOS system files through specially crafted HTTP resource requests.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-14558

CWE-78

Tenda

AC7, AC9, and AC10 Routers

CISAn julkaisema tietue ja toimenpide

Tenda AC7, AC9, and AC10 Routers Command Injection Vulnerability

Tenda AC7, AC9, and AC10 devices contain a command injection vulnerability due to the "formsetUsbUnload" function executes a dosystemCmd function with untrusted input. Successful exploitation allows an attacker to execute OS commands via a crafted goform/setUsbUnload request.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-15811

CWE-326

DotNetNuke (DNN)

DotNetNuke (DNN)

CISAn julkaisema tietue ja toimenpide

DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability

DotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-15961

CWE-434

Adobe

ColdFusion

CISAn julkaisema tietue ja toimenpide

Adobe ColdFusion Unrestricted File Upload Vulnerability

Adobe ColdFusion contains an unrestricted file upload vulnerability that could allow for code execution.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-18325

CWE-326

DotNetNuke (DNN)

DotNetNuke (DNN)

CISAn julkaisema tietue ja toimenpide

DotNetNuke (DNN) Inadequate Encryption Strength Vulnerability

DotNetNuke (DNN) contains an inadequate encryption strength vulnerability resulting from the use of a weak encryption algorithm to protect input parameters. This CVE ID resolves an incomplete patch for CVE-2018-15811.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-20062

CWE-20

ThinkPHP

noneCms

CISAn julkaisema tietue ja toimenpide

ThinkPHP "noneCms" Remote Code Execution Vulnerability

ThinkPHP "noneCms" contains an unspecified vulnerability that allows for remote code execution through crafted use of the filter parameter.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-2380

CWE-22

SAP

Customer Relationship Management (CRM)

CISAn julkaisema tietue ja toimenpide

SAP Customer Relationship Management (CRM) Path Traversal Vulnerability

SAP Customer Relationship Management (CRM) contains a path traversal vulnerability that allows an attacker to exploit insufficient validation of path information provided by users.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-4878

CWE-416

Adobe

Flash Player

CISAn julkaisema tietue ja toimenpide

Adobe Flash Player Use-After-Free Vulnerability

Adobe Flash Player contains a use-after-free vulnerability that could allow for code execution.

requiredAction
The impacted product is end-of-life and should be disconnected if still in use.
notes
https://nvd.nist.gov/vuln/detail/CVE-2018-4878

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-4939

CWE-502

Adobe

ColdFusion

CISAn julkaisema tietue ja toimenpide

Adobe ColdFusion Deserialization of Untrusted Data Vulnerability

Adobe ColdFusion contains a deserialization of untrusted data vulnerability that could allow for code execution.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2018-6789

CWE-119

Exim

Exim

CISAn julkaisema tietue ja toimenpide

Exim Buffer Overflow Vulnerability

Exim contains a buffer overflow vulnerability in the base64d function part of the SMTP listener that may allow for remote code execution.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-7600

CWE-20

Drupal

Drupal Core

CISAn julkaisema tietue ja toimenpide

Drupal Core Remote Code Execution Vulnerability

Drupal Core contains a remote code execution vulnerability that could allow an attacker to exploit multiple attack vectors on a Drupal site, resulting in complete site compromise.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2018-8653

CWE-787

Microsoft

Internet Explorer

CISAn julkaisema tietue ja toimenpide

Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability

Microsoft Internet Explorer contains a memory corruption vulnerability due to how the Scripting Engine handles objects in memory, leading to remote code execution.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2019-0211

CWE-416

Apache

HTTP Server

CISAn julkaisema tietue ja toimenpide

Apache HTTP Server Privilege Escalation Vulnerability

Apache HTTP Server, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute code with the privileges of the parent process (usually root) by manipulating the scoreboard.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2019-0541

CWE-77

Microsoft

MSHTML

CISAn julkaisema tietue ja toimenpide

Microsoft MSHTML Remote Code Execution Vulnerability

Microsoft MSHTML engine contains an improper input validation vulnerability that allows for remote code execution vulnerability.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2019-0604

CWE-20

Microsoft

SharePoint

CISAn julkaisema tietue ja toimenpide

Microsoft SharePoint Remote Code Execution Vulnerability

Microsoft SharePoint fails to check the source markup of an application package. An attacker who successfully exploits the vulnerability could run remote code in the context of the SharePoint application pool and the SharePoint server farm account.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2019-0708

CWE-416

Microsoft

Remote Desktop Services

CISAn julkaisema tietue ja toimenpide

Microsoft Remote Desktop Services Remote Code Execution Vulnerability

Microsoft Remote Desktop Services, formerly known as Terminal Service, contains an unspecified vulnerability that allows an unauthenticated attacker to connect to the target system using RDP and send specially crafted requests. Successful exploitation allows for remote code execution. The vulnerability is also known under the moniker of BlueKeep.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2019-0797

Microsoft

Win32k

CISAn julkaisema tietue ja toimenpide

Microsoft Win32k Privilege Escalation Vulnerability

Microsoft Win32k contains a privilege escalation vulnerability when the Win32k component fails to properly handle objects in memory. Successful exploitation allows an attacker to execute code in kernel mode.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2019-0803

Microsoft

Win32k

CISAn julkaisema tietue ja toimenpide

Microsoft Win32k Privilege Escalation Vulnerability

Microsoft Win32k contains an unspecified vulnerability due to it failing to properly handle objects in memory causing privilege escalation. Successful exploitation allows an attacker to run code in kernel mode.

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

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
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.

Lähdetiedot · CISA KEV

How we publish this official snapshot

Tämän kieliversion tarkemmat lähdekuvaukset ovat englanniksi.

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.

Tutki luetteloa ja menetelmää →

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.

Viralliset viitteet

Viitteet tukevat menetelmää. Sovita tarkastukset kontekstiisi; ne eivät ole sertifiointia. Alkuperäiset viitteiden otsikot ja lähdeasiakirjat voivat olla toisella kielellä.

Lähteet tarkistettu .