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
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
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
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
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
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
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
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
| Indikaattori | Mitä se mittaa | Ensimmäinen toimenpide |
|---|---|---|
| Kattavuus | Kriittiset resurssit, joilla on tunnetut versiot ja omistajat | Täydennä luettelo |
| Viivästys | Aika hyväksynnästä varmennettuun korjaukseen | Poista toistuvat pullonkaulat |
| Varmennus | Korjaukset testattu uudelleen reaaliresursseilla | Avaa sulkemiset uudelleen ilman todisteita |
| Poikkeukset | Vapautukset, joihin liittyy hallinta, omistaja ja vanheneminen | Sulje 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.
| Lähde ja tarkoitus | Tarkistettu tieto tai vertailukohta | Kä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. | 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 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 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
| Source | Useful question | What it cannot establish alone |
|---|---|---|
| CVSS 4.0 | What is the technical severity under the assessed metrics? | The score proves neither exploitation nor consequences for your service. |
| EPSS | What 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 KEV | Is the vulnerability listed as known to be exploited? | Listing does not establish that the product exists in your estate; absence does not establish safety. |
| VEX | What 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.
| Group | Role | Reading check |
|---|---|---|
| Base | Intrinsic vulnerability characteristics. | A supplier’s CVSS-B is not your priority decision. |
| Threat | Threat characteristics that can change over time. | Date the assessment and explain exploitation information used. |
| Environmental | Characteristics specific to the consumer’s environment. | State the controls and system importance considered rather than silently changing a score. |
| Supplemental | Additional 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.
| Fictional example | Provided values | Correct reading |
|---|---|---|
| A probability | Probability : 0.05 · Percentile : Unspecified | 0.05 means a 5% estimated probability of observed exploitation within the model horizon, rather than an estate compromise rate. |
| Probability and rank | Probability : 0.02 · Percentile : 0.97 | In 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 value | Probability : Unspecified · Percentile : Unspecified | Missing 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.
| Fields | Meaning | Proposed check |
|---|---|---|
| catalogVersion / dateReleased | Catalogue version and publication time. | Keep a reference to the consulted edition; distinguish publication time from your assessment time. |
| cveID / vendorProject / product | Identifier and product associated with the entry. | Match name, version, distribution and embedded components before declaring an asset affected. |
| dateAdded | Date the vulnerability entered the catalogue. | Do not present it as the first exploitation date or CVE publication date. |
| requiredAction | Requested action to address the vulnerability. | Read the complete instruction and supplier references, then document local implementation. |
| dueDate | Catalogue deadline for the requested action. | Check the context and scope of the CISA instruction before adopting it as a local deadline. |
| knownRansomwareCampaignUse | Known indicates confirmed ransomware campaign use; Unknown means CISA lacks confirmation. | Do not translate Unknown into never used or a definite false value. |
| cwes | Weakness 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
- FIRST · CVSS 4.0 Specification · CVSS 4.0 · document 1.2 · reviewed 2026-10-22
Overview · Assessment · Nomenclature · Supplemental Metrics - FIRST · EPSS Frequently Asked Questions · Living FAQ · reviewed 2026-10-22
What is EPSS? · Reading the score · Percentile · Score changes - CISA · KEV official data schema · Official CISA mirror · reviewed 2026-10-22
Catalog properties · vulnerability properties · required fields - OpenVEX · Specification v0.2.0 · OpenVEX v0.2.0 · reviewed 2026-10-22
Statement Data Structure · Status Labels · Status Justifications · Data Inheritance
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
| Published field | Useful reading | Conclusion to avoid |
|---|---|---|
| cveID | Join sources discussing the same vulnerability. | The identifier year does not date KEV inclusion. |
| vendorProject · product | Find the vendor advisory and local inventory. | A product name does not replace affected versions and configurations. |
| dateAdded | Date the entry’s inclusion in this catalogue. | Do not call it discovery or first-exploitation date. |
| dueDate · requiredAction | Read the published action and deadline together. | Do not turn the date into a universal obligation or proof of remediation. |
| knownRansomwareCampaignUse | Preserve Known, Unknown or an absent field. | Unknown is not No and does not remove the known exploitation signal underlying KEV. |
| forensicTriage · cwes | Separate 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
| Lisäysvuosi | Tietueet |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
Tulokset : 187 / 1769 · Sivu 1 / 8
| CVE | Toimittaja tai projekti · product | Lisäyspäivä / Tietueen määräpäivä | Käyttö kiristyshaittaohjelmakampanjoissa / forensicTriage |
|---|---|---|---|
| CVE-2023-47565 CWE-78 | QNAP VioStor NVR CISAn julkaisema tietue ja toimenpideQNAP VioStor NVR OS Command Injection VulnerabilityQNAP VioStar NVR contains an OS command injection vulnerability that allows authenticated users to execute commands via a network.
|
|
|
| CVE-2023-49897 CWE-78 | FXC AE1021, AE1021PE CISAn julkaisema tietue ja toimenpideFXC AE1021, AE1021PE OS Command Injection VulnerabilityFXC AE1021 and AE1021PE contain an OS command injection vulnerability that allows authenticated users to execute commands via a network.
|
|
|
| CVE-2023-6448 CWE-1188 | Unitronics Vision PLC and HMI CISAn julkaisema tietue ja toimenpideUnitronics Vision PLC and HMI Insecure Default Password VulnerabilityUnitronics Vision Series PLCs and HMIs ship with an insecure default password, which if left unchanged, can allow attackers to execute remote commands.
|
|
|
| CVE-2023-41265 CWE-444 | Qlik Sense CISAn julkaisema tietue ja toimenpideQlik Sense HTTP Tunneling VulnerabilityQlik Sense contains an HTTP tunneling vulnerability that allows an attacker to escalate privileges and execute HTTP requests on the backend server hosting the software.
|
|
|
| CVE-2023-41266 CWE-20 | Qlik Sense CISAn julkaisema tietue ja toimenpideQlik Sense Path Traversal VulnerabilityQlik Sense contains a path traversal vulnerability that allows a remote, unauthenticated attacker to create an anonymous session by sending maliciously crafted HTTP requests. This anonymous session could allow the attacker to send further requests to unauthorized endpoints.
|
|
|
| CVE-2022-22071 CWE-416 | Qualcomm Multiple Chipsets CISAn julkaisema tietue ja toimenpideQualcomm Multiple Chipsets Use-After-Free VulnerabilityMultiple Qualcomm chipsets contain a use-after-free vulnerability when process shell memory is freed using IOCTL munmap call and process initialization is in progress.
|
|
|
| CVE-2023-33063 CWE-416 | Qualcomm Multiple Chipsets CISAn julkaisema tietue ja toimenpideQualcomm Multiple Chipsets Use-After-Free VulnerabilityMultiple Qualcomm chipsets contain a use-after-free vulnerability due to memory corruption in DSP Services during a remote call from HLOS to DSP.
|
|
|
| CVE-2023-33106 CWE-823 | Qualcomm Multiple Chipsets CISAn julkaisema tietue ja toimenpideQualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset VulnerabilityMultiple Qualcomm chipsets contain a use of out-of-range pointer offset vulnerability due to memory corruption in Graphics while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.
|
|
|
| CVE-2023-33107 CWE-190 | Qualcomm Multiple Chipsets CISAn julkaisema tietue ja toimenpideQualcomm Multiple Chipsets Integer Overflow VulnerabilityMultiple Qualcomm chipsets contain an integer overflow vulnerability due to memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.
|
|
|
| CVE-2023-42916 CWE-125 | Apple Multiple Products CISAn julkaisema tietue ja toimenpideApple Multiple Products WebKit Out-of-Bounds Read VulnerabilityApple iOS, iPadOS, macOS, and Safari WebKit contain an out-of-bounds read vulnerability that may disclose sensitive information when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.
|
|
|
| CVE-2023-42917 CWE-787 | Apple Multiple Products CISAn julkaisema tietue ja toimenpideApple Multiple Products WebKit Memory Corruption VulnerabilityApple iOS, iPadOS, macOS, and Safari WebKit contain a memory corruption vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.
|
|
|
| CVE-2023-49103 | ownCloud ownCloud graphapi CISAn julkaisema tietue ja toimenpideownCloud graphapi Information Disclosure VulnerabilityownCloud graphapi contains an information disclosure vulnerability that can reveal sensitive data stored in phpinfo() via GetPhpInfo.php, including administrative credentials.
|
|
|
| CVE-2023-6345 CWE-190 | Google Chromium Skia CISAn julkaisema tietue ja toimenpideGoogle Skia Integer Overflow VulnerabilityGoogle Chromium Skia contains an integer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a malicious file. This vulnerability affects Google Chrome and ChromeOS, Android, Flutter, and possibly other products.
|
|
|
| CVE-2023-4911 CWE-122 | GNU GNU C Library CISAn julkaisema tietue ja toimenpideGNU C Library Buffer Overflow VulnerabilityGNU C Library's dynamic loader ld.so contains a buffer overflow vulnerability when processing the GLIBC_TUNABLES environment variable, allowing a local attacker to execute code with elevated privileges.
|
|
|
| CVE-2020-2551 | Oracle Fusion Middleware CISAn julkaisema tietue ja toimenpideOracle Fusion Middleware Unspecified VulnerabilityOracle Fusion Middleware contains an unspecified vulnerability in the WLS Core Components that allows an unauthenticated attacker with network access via IIOP to compromise the WebLogic Server.
|
|
|
| CVE-2023-1671 CWE-77 | Sophos Web Appliance CISAn julkaisema tietue ja toimenpideSophos Web Appliance Command Injection VulnerabilitySophos Web Appliance contains a command injection vulnerability in the warn-proceed handler that allows for remote code execution.
|
|
|
| CVE-2023-36584 | Microsoft Windows CISAn julkaisema tietue ja toimenpideMicrosoft Windows Mark of the Web (MOTW) Security Feature Bypass VulnerabilityMicrosoft Windows Mark of the Web (MOTW) contains a security feature bypass vulnerability resulting in a limited loss of integrity and availability of security features.
|
|
|
| CVE-2023-36025 | Microsoft Windows CISAn julkaisema tietue ja toimenpideMicrosoft Windows SmartScreen Security Feature Bypass VulnerabilityMicrosoft Windows SmartScreen contains a security feature bypass vulnerability that could allow an attacker to bypass Windows Defender SmartScreen checks and their associated prompts.
|
|
|
| CVE-2023-36033 CWE-822 | Microsoft Windows CISAn julkaisema tietue ja toimenpideMicrosoft Windows Desktop Window Manager (DWM) Core Library Privilege Escalation VulnerabilityMicrosoft Windows Desktop Window Manager (DWM) Core Library contains an unspecified vulnerability that allows for privilege escalation.
|
|
|
| CVE-2023-36036 CWE-122 | Microsoft Windows CISAn julkaisema tietue ja toimenpideMicrosoft Windows Cloud Files Mini Filter Driver Privilege Escalation VulnerabilityMicrosoft Windows Cloud Files Mini Filter Driver contains a privilege escalation vulnerability that could allow an attacker to gain SYSTEM privileges.
|
|
|
| CVE-2023-36844 CWE-473 | Juniper Junos OS CISAn julkaisema tietue ja toimenpideJuniper Junos OS EX Series PHP External Variable Modification VulnerabilityJuniper Junos OS on EX Series contains a PHP external variable modification vulnerability that allows an unauthenticated, network-based attacker to control certain, important environment variables. Using a crafted request an attacker is able to modify certain PHP environment variables, leading to partial loss of integrity, which may allow chaining to other vulnerabilities.
|
|
|
| CVE-2023-36845 CWE-473 | Juniper Junos OS CISAn julkaisema tietue ja toimenpideJuniper Junos OS EX Series and SRX Series PHP External Variable Modification VulnerabilityJuniper Junos OS on EX Series and SRX Series contains a PHP external variable modification vulnerability that allows an unauthenticated, network-based attacker to control an important environment variable. Using a crafted request, which sets the variable PHPRC, an attacker is able to modify the PHP execution environment allowing the injection und execution of code.
|
|
|
| CVE-2023-36846 CWE-306 | Juniper Junos OS CISAn julkaisema tietue ja toimenpideJuniper Junos OS SRX Series Missing Authentication for Critical Function VulnerabilityJuniper Junos OS on SRX Series contains a missing authentication for critical function vulnerability that allows an unauthenticated, network-based attacker to cause limited impact to the file system integrity. With a specific request to user.php that doesn't require authentication, an attacker is able to upload arbitrary files via J-Web, leading to a loss of integrity for a certain part of the file system, which may allow chaining to other vulnerabilities.
|
|
|
| CVE-2023-36847 CWE-306 | Juniper Junos OS CISAn julkaisema tietue ja toimenpideJuniper Junos OS EX Series Missing Authentication for Critical Function VulnerabilityJuniper Junos OS on EX Series contains a missing authentication for critical function vulnerability that allows an unauthenticated, network-based attacker to cause limited impact to the file system integrity. With a specific request to installAppPackage.php that doesn't require authentication, an attacker is able to upload arbitrary files via J-Web, leading to a loss of integrity for a certain part of the file system, which may allow chaining to other vulnerabilities.
|
|
|
| CVE-2023-36851 CWE-306 | Juniper Junos OS CISAn julkaisema tietue ja toimenpideJuniper Junos OS SRX Series Missing Authentication for Critical Function VulnerabilityJuniper Junos OS on SRX Series contains a missing authentication for critical function vulnerability that allows an unauthenticated, network-based attacker to cause limited impact to the file system integrity. With a specific request to webauth_operation.php that doesn't require authentication, an attacker is able to upload arbitrary files via J-Web, leading to a loss of integrity for a certain part of the file system, which may allow chaining to other vulnerabilities.
|
|
|
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
- 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.
- 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.
- Document the change
Assign an owner, prepare rollback and verify dependencies. A mitigation remains a scoped measure with an explicit validity period.
- 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 official snapshot · 2026.11.06
- CISA · Current KEV JSON in the official repository · Live repository file
- CISA · KEV data schema · JSON Schema Draft 07 · pinned source
- CISA · Official mirror and reuse terms · Official repository · pinned source
- CISA · KEV licence · CC0 1.0 Universal
- FedRAMP · Response to CISA BOD 26-04 · Notice NTC-0014 · 16 June 2026
- FIRST · CVSS · CVSS 4.0
- FIRST · EPSS · Living documentation · reviewed 2026-10-22
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 official snapshot · 2026.11.06
- CISA · Current KEV JSON in the official repository · Live repository file
- CISA · KEV data schema · JSON Schema Draft 07 · pinned source
- CISA · Official mirror and reuse terms · Official repository · pinned source
- CISA · KEV licence · CC0 1.0 Universal
- FedRAMP · Response to CISA BOD 26-04 · Notice NTC-0014 · 16 June 2026
- FIRST · CVSS · CVSS 4.0
- FIRST · EPSS · Living documentation · reviewed 2026-10-22
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 .
- NIST SP 800-40 Rev. 4 — enterprise patch management
- CISA — Known Exploited Vulnerabilities Catalog
- FIRST · CVSS
- FIRST · EPSS
- CISA · Known Exploited Vulnerabilities
- 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 official snapshot
- CISA · Current KEV JSON in the official repository
- CISA · KEV data schema
- CISA · Official mirror and reuse terms
- CISA · KEV licence
- FedRAMP · Response to CISA BOD 26-04
- FIRST · CVSS
- FIRST · EPSS Frequently Asked Questions
- CISA · KEV official data schema
- OpenVEX · Specification v0.2.0
