참고 자료 · 23
취약점의 우선순위를 정하고 해결 방안을 검증합니다.
알려진 악용 사례, 노출된 자산, 비즈니스 영향 및 작동하는 수정 사항에 대한 증거를 연결합니다.
업데이트됨 · 20 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. |
연도별 목록 추가 건수
결과 : 187 / 1769 · 페이지 6 / 8
| CVE | 공급업체 또는 프로젝트 · product | 등록일 / 항목에 기재된 기한 | 랜섬웨어 캠페인에서 사용 / forensicTriage |
|---|---|---|---|
| CVE-2016-3427 | Oracle Java SE and JRockit CISA가 공개한 항목과 조치Oracle Java SE and JRockit Unspecified VulnerabilityOracle Java SE and JRockit contains an unspecified vulnerability that allows remote attackers to affect confidentiality, integrity, and availability via vectors related to Java Management Extensions (JMX). This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It can also be exploited by supplying data to APIs in the specified component without using sandboxed Java Web Start applications or sandboxed Java applets, such as through a web service.
|
|
|
| CVE-2016-8735 CWE-284 | Apache Tomcat CISA가 공개한 항목과 조치Apache Tomcat Remote Code Execution VulnerabilityApache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports. This CVE exists because this listener wasn't updated for consistency with the Oracle patched issues for CVE-2016-3427 which affected credential types.
|
|
|
| CVE-2021-3560 CWE-863 | Red Hat Polkit CISA가 공개한 항목과 조치Red Hat Polkit Incorrect Authorization VulnerabilityRed Hat Polkit contains an incorrect authorization vulnerability through the bypassing of credential checks for D-Bus requests, allowing for privilege escalation.
|
|
|
| CVE-2023-25717 CWE-94 | Ruckus Wireless Multiple Products CISA가 공개한 항목과 조치Multiple Ruckus Wireless Products CSRF and RCE VulnerabilityRuckus Wireless Access Point (AP) software contains an unspecified vulnerability in the web services component. If the web services component is enabled on the AP, an attacker can perform cross-site request forgery (CSRF) or remote code execution (RCE). This vulnerability impacts Ruckus ZoneDirector, SmartZone, and Solo APs.
|
|
|
| CVE-2023-29336 CWE-416 | Microsoft Win32k CISA가 공개한 항목과 조치Microsoft Win32K Privilege Escalation VulnerabilityMicrosoft Win32k contains an unspecified vulnerability that allows for privilege escalation up to SYSTEM privileges.
|
|
|
| CVE-2021-45046 CWE-917 | Apache Log4j2 CISA가 공개한 항목과 조치Apache Log4j2 Deserialization of Untrusted Data VulnerabilityApache Log4j2 contains a deserialization of untrusted data vulnerability due to the incomplete fix of CVE-2021-44228, where the Thread Context Lookup Pattern is vulnerable to remote code execution in certain non-default configurations.
|
|
|
| CVE-2023-1389 CWE-77 | TP-Link Archer AX21 CISA가 공개한 항목과 조치TP-Link Archer AX-21 Command Injection VulnerabilityTP-Link Archer AX-21 contains a command injection vulnerability that allows for remote code execution.
|
|
|
| CVE-2023-21839 | Oracle WebLogic Server CISA가 공개한 항목과 조치Oracle WebLogic Server Unspecified VulnerabilityOracle WebLogic Server contains an unspecified vulnerability that allows an unauthenticated attacker with network access via T3, IIOP, to compromise Oracle WebLogic Server.
|
|
|
| CVE-2023-2136 CWE-190 | Google Chromium Skia CISA가 공개한 항목과 조치Google Chrome 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 crafted HTML page. This vulnerability affects Google Chrome and ChromeOS, Android, Flutter, and possibly other products.
|
|
|
| CVE-2023-27350 CWE-284 | PaperCut MF/NG CISA가 공개한 항목과 조치PaperCut MF/NG Improper Access Control VulnerabilityPaperCut MF/NG contains an improper access control vulnerability within the SetupCompleted class that allows authentication bypass and code execution in the context of system.
|
|
|
| CVE-2023-28432 CWE-200 | MinIO MinIO CISA가 공개한 항목과 조치MinIO Information Disclosure VulnerabilityMinIO contains a vulnerability in a cluster deployment where MinIO returns all environment variables, which allows for information disclosure.
|
|
|
| CVE-2017-6742 CWE-119 | Cisco IOS and IOS XE Software CISA가 공개한 항목과 조치Cisco IOS and IOS XE Software SNMP Remote Code Execution VulnerabilityThe Simple Network Management Protocol (SNMP) subsystem of Cisco IOS and IOS XE contains a vulnerability that could allow an authenticated, remote attacker to remotely execute code on an affected system or cause an affected system to reload.
|
|
|
| CVE-2019-8526 CWE-416 | Apple macOS CISA가 공개한 항목과 조치Apple macOS Use-After-Free VulnerabilityApple macOS contains a use-after-free vulnerability that could allow for privilege escalation.
|
|
|
| CVE-2023-2033 CWE-843 | Google Chromium V8 CISA가 공개한 항목과 조치Google Chromium V8 Type Confusion VulnerabilityGoogle Chromium V8 Engine contains a type confusion 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-2023-20963 CWE-295 | Android Framework CISA가 공개한 항목과 조치Android Framework Privilege Escalation VulnerabilityAndroid Framework contains an unspecified vulnerability that allows for privilege escalation after updating an app to a higher Target SDK with no additional execution privileges needed.
|
|
|
| CVE-2023-29492 CWE-94 | Novi Survey Novi Survey CISA가 공개한 항목과 조치Novi Survey Insecure Deserialization VulnerabilityNovi Survey contains an insecure deserialization vulnerability that allows remote attackers to execute code on the server in the context of the service account.
|
|
|
| CVE-2023-28252 CWE-122 | Microsoft Windows CISA가 공개한 항목과 조치Microsoft Windows Common Log File System (CLFS) Driver Privilege Escalation VulnerabilityMicrosoft Windows Common Log File System (CLFS) driver contains an unspecified vulnerability that allows for privilege escalation.
|
|
|
| CVE-2023-28205 CWE-416 | Apple Multiple Products CISA가 공개한 항목과 조치Apple Multiple Products WebKit Use-After-Free VulnerabilityApple iOS, iPadOS, macOS, and Safari WebKit contain a use-after-free 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-28206 CWE-787 | Apple iOS, iPadOS, and macOS CISA가 공개한 항목과 조치Apple iOS, iPadOS, and macOS IOSurfaceAccelerator Out-of-Bounds Write VulnerabilityApple iOS, iPadOS, and macOS IOSurfaceAccelerator contain an out-of-bounds write vulnerability that allows an app to execute code with kernel privileges.
|
|
|
| CVE-2019-1388 CWE-269 | Microsoft Windows CISA가 공개한 항목과 조치Microsoft Windows Certificate Dialog Privilege Escalation VulnerabilityMicrosoft Windows Certificate Dialog contains a privilege escalation vulnerability, allowing attackers to run processes in an elevated context.
|
|
|
| CVE-2021-27876 CWE-287 | Veritas Backup Exec Agent CISA가 공개한 항목과 조치Veritas Backup Exec Agent File Access VulnerabilityVeritas Backup Exec (BE) Agent contains a file access vulnerability that could allow an attacker to specially craft input parameters on a data management protocol command to access files on the BE Agent machine.
|
|
|
| CVE-2021-27877 CWE-287 | Veritas Backup Exec Agent CISA가 공개한 항목과 조치Veritas Backup Exec Agent Improper Authentication VulnerabilityVeritas Backup Exec (BE) Agent contains an improper authentication vulnerability that could allow an attacker unauthorized access to the BE Agent via SHA authentication scheme.
|
|
|
| CVE-2021-27878 CWE-287 | Veritas Backup Exec Agent CISA가 공개한 항목과 조치Veritas Backup Exec Agent Command Execution VulnerabilityVeritas Backup Exec (BE) Agent contains a command execution vulnerability that could allow an attacker to use a data management protocol command to execute a command on the BE Agent machine.
|
|
|
| CVE-2023-26083 CWE-401 | Arm Mali Graphics Processing Unit (GPU) CISA가 공개한 항목과 조치Arm Mali GPU Kernel Driver Information Disclosure VulnerabilityArm Mali GPU Kernel Driver contains an information disclosure vulnerability that allows a non-privileged user to make valid GPU processing operations that expose sensitive kernel metadata.
|
|
|
| CVE-2022-27926 CWE-79, CWE-138 | Synacor Zimbra Collaboration Suite (ZCS) CISA가 공개한 항목과 조치Synacor Zimbra Collaboration Suite (ZCS) Cross-Site Scripting (XSS) VulnerabilitySynacor Zimbra Collaboration Suite (ZCS) contains a cross-site scripting vulnerability by allowing an endpoint URL to accept parameters without sanitizing.
|
|
|
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
