الموارد · 23
تحديد أولويات الثغرات الأمنية والتحقق من معالجتها.
ربط الاستغلال المعروف، والأصول المعرضة للخطر، وتأثيرها على الأعمال، وإثبات فعالية الإصلاح.
مُحدَّث · 9 min
ما يُساعد هذا الدليل على تحقيقه
- مطابقة التنبيهات مع الأصول
- تحديد مستوى الأهمية الفعلية
- النشر الآمن
- التحقق والإغلاق
فحص سريع
- هل تم نشر المنتج والإصدار المتأثرين بالفعل؟
- هل الأصل قابل للوصول إليه وذو أهمية بالغة للعمل؟
- هل تم توثيق الاستغلال؟
- ما الذي يحمي الخدمة قبل تطبيق التصحيح؟
- هل يؤكد الفحص زوال المشكلة من الأصل؟
طريقة خطوة بخطوة
- 1
توحيد المخزون
تحديد الخدمات والمنتجات والإصدارات والبيئات ومستويات التعرض والمالكين. لا يثبت وجود إشعار استشاري للمكون وحده نشر نسخة معرضة للخطر.
المُخرَج: قائمة مؤرخة بالأصول المتأثرة ومصادر عدم اليقين.
- 2
تحديد طبيعة النتيجة
مقارنة إشعار المورّد، ومعرّف CVE، وشروط الاستغلال، وعند الاقتضاء، قائمة الثغرات الأمنية المعروفة والمستغلة من قِبل وكالة الأمن السيبراني وأمن البنية التحتية (CISA). تسجيل تاريخ فحص كل مصدر.
المُخرَج: النتيجة مع المراجع الأساسية.
- 3
تحديد أولوية قابلة للدفاع
مراعاة الاستغلال المعروف، وإمكانية الوصول إلى الأصول، والصلاحيات المطلوبة، والبيانات المُعالَجة، وتأثير الخدمة، والحلول المتاحة. تعيين مسؤول وتحديد موعد نهائي مناسب للسياق.
المُخرَج: قرار مُبرَّر بشأن الأولوية.
- 4
تجهيز التغيير
تحديد التبعيات، وفترة التغيير، والنسخ الاحتياطي، والتراجع. في حال تعذّر تطبيق التحديث فورًا، تسجيل التحكم المؤقت وتاريخ انتهائه.
المُخرَج: خطة النشر والاستثناءات المحدودة.
- 5
النشر والاختبار
تطبيق إصلاح المورّد أو التخفيف باستخدام العملية المعتمدة. تحقق من الإصدار الناتج، ومسار العمل، وعمليات التكامل التي قد تتراجع.
المُخرَج: سجل النشر والنتيجة الوظيفية.
- 6
التحقق من الإغلاق.
التحقق من الأصل الفعلي باستخدام طريقة مناسبة، وتحديد الحالات المفقودة، وإعادة النظر في الاستثناءات. لا تُغلق تذكرة لمجرد جدولة تحديث.
المُخرَج: دليل التحقق والسجل المُحدَّث.
مؤشرات الإدارة
| المؤشر | ما يقيسه | الإجراء الأول |
|---|---|---|
| التغطية | الأصول الحيوية ذات الإصدارات والمالكين المعروفين | إكمال الجرد |
| التأخير | الوقت من التأهيل إلى الإصلاح المُعتمد | إزالة الاختناقات المتكررة |
| التحقق | إعادة اختبار الإصلاحات على أصول حقيقية | إعادة فتح حالات الإغلاق بدون دليل |
| الاستثناءات | التنازلات مع التحكم والمالك وتاريخ الانتهاء | إغلاق الاستثناءات منتهية الصلاحية |
الأخطاء الشائعة
- التصنيف بناءً على درجة عامة فقط دون التحقق من الأصل
- افتراض أن إدراج KEV يعني وجود المنتج في مؤسستك
- النشر دون اختبار سلوك الخدمة
- ترك ضوابط تعويضية بدون تاريخ مراجعة
الأسئلة المتكررة
هل يجب دائمًا معالجة CVE الأعلى درجة أولاً؟
تصف الدرجة الخطورة التقنية؛ ويُوجه ترتيبك التشغيلي بناءً على الاستغلال المعروف والتعرض وتأثير الخدمة المحلية.
ماذا لو لم تكن هناك رقعة تصحيحية؟
اتبع إجراءات التخفيف التي اتخذها المورّد، وقلّل المخاطر قدر الإمكان، ووثّق المسؤول، وتاريخ المراجعة، والمخاطر المتبقية.
متى يُعتبر العمل منتهيًا؟
بعد التحقق من الإصدار أو إجراء التخفيف على الأنظمة المتأثرة، واختبار الوظائف الأساسية.
المراجع: البيانات والاستخدامات والحدود
تاريخ مراجعة الوثائق .
الملاحظات المرجعية المفصّلة متاحة باللغة الإنجليزية في هذه النسخة.
| المصدر والغرض | بيانات أو معيار متحقق منه | كيفية الاستخدام | حدود يجب مراعاتها |
|---|---|---|---|
| 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 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
توقيع البناء ومصدره
الملاحظات المرجعية المفصّلة متاحة باللغة الإنجليزية في هذه النسخة.
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
| 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. |
الإضافات إلى الكتالوج حسب السنة
| سنة الإضافة | السجلات |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
النتائج : 1769 / 1769 · الصفحة 59 / 71
| CVE | المورّد أو المشروع · product | تاريخ الإضافة / الموعد في السجل | الاستخدام في حملات برامج الفدية / forensicTriage |
|---|---|---|---|
| CVE-2019-1579 CWE-134 | Palo Alto Networks PAN-OS السجل والإجراء المنشوران من CISAPalo Alto Networks PAN-OS Remote Code Execution VulnerabilityRemote Code Execution in PAN-OS with GlobalProtect Portal or GlobalProtect Gateway Interface enabled.
|
|
|
| CVE-2019-2725 CWE-74 | Oracle WebLogic Server السجل والإجراء المنشوران من CISAOracle WebLogic Server, InjectionInjection vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Web Services).
|
|
|
| CVE-2019-7609 CWE-94 | Elastic Kibana السجل والإجراء المنشوران من CISAKibana Arbitrary Code ExecutionKibana contain an arbitrary code execution flaw in the Timelion visualizer.
|
|
|
| CVE-2019-9670 CWE-611 | Synacor Zimbra Collaboration Suite (ZCS) السجل والإجراء المنشوران من CISASynacor Zimbra Collaboration Suite (ZCS) Improper Restriction of XML External Entity ReferenceSynacor Zimbra Collaboration Suite (ZCS) contains an improper restriction of XML external entity (XXE) vulnerability in the mailboxd component.
|
|
|
| CVE-2020-6572 CWE-416 | Google Chrome Media السجل والإجراء المنشوران من CISAGoogle Chrome Media Use-After-Free VulnerabilityGoogle Chrome Media contains a use-after-free vulnerability that allows a remote attacker to execute code via a crafted HTML page.
|
|
|
| CVE-2021-22017 CWE-23 | VMware vCenter Server السجل والإجراء المنشوران من CISAVMware vCenter Server Improper Access ControlRhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization.
|
|
|
| CVE-2021-27860 CWE-434 | FatPipe WARP, IPVPN, and MPVPN software السجل والإجراء المنشوران من CISAFatPipe WARP, IPVPN, and MPVPN Configuration Upload exploitA vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN software allows a remote, unauthenticated attacker to upload a file to any location on the filesystem.
|
|
|
| CVE-2021-36260 CWE-78 | Hikvision Security cameras web server السجل والإجراء المنشوران من CISAHikvision Improper Input ValidationA command injection vulnerability in the web server of some Hikvision product. Due to the insufficient input validation.
|
|
|
| CVE-2021-4102 CWE-416 | Google Chromium V8 السجل والإجراء المنشوران من CISAGoogle Chromium V8 Use-After-Free VulnerabilityGoogle Chromium V8 Engine contains a use-after-free vulnerability that 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.
|
|
|
| CVE-2021-43890 | Microsoft Windows السجل والإجراء المنشوران من CISAMicrosoft Windows AppX Installer Spoofing VulnerabilityMicrosoft Windows AppX Installer contains a spoofing vulnerability which has a high impacts to confidentiality, integrity, and availability.
|
|
|
| CVE-2010-1871 CWE-20 | Red Hat JBoss Seam 2 السجل والإجراء المنشوران من CISARed Hat Linux JBoss Seam 2 Remote Code Execution VulnerabilityJBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, allows attackers to perform remote code execution. This vulnerability can only be exploited when the Java Security Manager is not properly configured.
|
|
|
| CVE-2017-12149 CWE-502 | Red Hat JBoss Application Server السجل والإجراء المنشوران من CISARed Hat JBoss Application Server Remote Code Execution VulnerabilityThe JBoss Application Server, shipped with Red Hat Enterprise Application Platform 5.2, allows an attacker to execute arbitrary code via crafted serialized data.
|
|
|
| CVE-2017-17562 CWE-20 | Embedthis GoAhead السجل والإجراء المنشوران من CISAEmbedthis GoAhead Remote Code Execution VulnerabilityEmbedthis GoAhead before 3.6.5 allows remote code execution if CGI is enabled and a CGI program is dynamically linked.
|
|
|
| CVE-2019-0193 CWE-94 | Apache Solr السجل والإجراء المنشوران من CISAApache Solr DataImportHandler Code Injection VulnerabilityThe optional Apache Solr module DataImportHandler contains a code injection vulnerability.
|
|
|
| CVE-2019-10758 | MongoDB mongo-express السجل والإجراء المنشوران من CISAMongoDB mongo-express Remote Code Execution Vulnerabilitymongo-express before 0.54.0 is vulnerable to Remote Code Execution via endpoints that uses the `toBSON` method.
|
|
|
| CVE-2019-13272 CWE-269 | Linux Kernel السجل والإجراء المنشوران من CISALinux Kernel Improper Privilege Management VulnerabilityKernel/ptrace.c in Linux kernel mishandles contains an improper privilege management vulnerability that allows local users to obtain root access.
|
|
|
| CVE-2019-7238 | Sonatype Nexus Repository Manager السجل والإجراء المنشوران من CISASonatype Nexus Repository Manager Incorrect Access Control VulnerabilitySonatype Nexus Repository Manager before 3.15.0 has an incorrect access control vulnerability. Exploitation allows for remote code execution.
|
|
|
| CVE-2020-17463 CWE-89 | Fuel CMS Fuel CMS السجل والإجراء المنشوران من CISAFuel CMS SQL Injection VulnerabilityFUEL CMS 1.4.7 allows SQL Injection via the col parameter to /pages/items, /permissions/items, or /navigation/items.
|
|
|
| CVE-2020-8816 CWE-78 | Pi-hole AdminLTE السجل والإجراء المنشوران من CISAPi-Hole AdminLTE Remote Code Execution VulnerabilityPi-hole Web v4.3.2 (aka AdminLTE) allows Remote Code Execution by privileged dashboard users via a crafted DHCP static lease.
|
|
|
| CVE-2021-35394 CWE-78, CWE-138 | Realtek Jungle Software Development Kit (SDK) السجل والإجراء المنشوران من CISARealtek Jungle SDK Remote Code Execution VulnerabilityRealTek Jungle SDK contains multiple memory corruption vulnerabilities which can allow an attacker to perform remote code execution.
|
|
|
| CVE-2021-44168 CWE-494 | Fortinet FortiOS السجل والإجراء المنشوران من CISAFortinet FortiOS Arbitrary File DownloadFortinet FortiOS "execute restore src-vis" downloads code without integrity checking, allowing an attacker to arbitrarily download files.
|
|
|
| CVE-2021-44228 CWE-20, CWE-400, CWE-502 | Apache Log4j2 السجل والإجراء المنشوران من CISAApache Log4j2 Remote Code Execution VulnerabilityApache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.
|
|
|
| CVE-2021-44515 | Zoho Desktop Central السجل والإجراء المنشوران من CISAZoho Desktop Central Authentication Bypass VulnerabilityZoho Desktop Central contains an authentication bypass vulnerability that could allow an attacker to execute arbitrary code in the Desktop Central MSP server.
|
|
|
| CVE-2018-14847 CWE-22 | MikroTik RouterOS السجل والإجراء المنشوران من CISAMikroTik Router OS Directory Traversal VulnerabilityMikroTik RouterOS through 6.42 allows unauthenticated remote attackers to read arbitrary files and remote authenticated attackers to write arbitrary files due to a directory traversal vulnerability in the WinBox interface.
|
|
|
| CVE-2020-11261 CWE-20 | Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables السجل والإجراء المنشوران من CISAQualcomm Multiple Chipsets Improper Input Validation VulnerabilityMemory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
|
|
|
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.
معلومات مرجعية · 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 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.
المراجع الرسمية
تدعم المراجع الطريقة. قم بتكييف عمليات التحقق مع سياقك؛ فهي ليست شهادة. قد تكون عناوين المراجع الأصلية والوثائق المصدرية بلغة أخرى.
تاريخ مراجعة المراجع .
- 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
