{"type":"api","title":"Get one Vulnerability by ID","meta":{"id":"/apps/pubhub/media/cisco-xdr-api-docs/f4e065ff5977829c89df289df08411f83205f526/2c61df32-bc97-34af-969d-a2ce06b8e459","info":{"title":"CTIA","description":"A Threat Intelligence API service\n\n This API provides a mechanism for making Judgements on the Disposition\n of Observables, which are then distilled into a final Verdict. A\n Disposition is a statement regarding the malicious, or otherwise,\n nature of an Observable.\n\n The Judgements can be grouped into Indicators, which can be associated\n with Campaigns, Actors and TTPs. Feedback can be given on specific\n Judgements, indicating agreement or disagreement, or clarification.\n\n When an Observable with a malicious Verdict is seen, it can be recorded as\n a Sighting, and the Relations that Observable had with other Observables can\n be recorded as well.\n\n We support a pre-defined set of Observable Types. Each Observable Type has a\n specific form of natural identifier, its ID, which is almost always\n the default way it is represented when observed in the wild.\n\n * Ipv4/IPv6 -- 192.168.1.1\n * Domain/Hostname -- foo.com, www.bar.com\n * SHA256 -- the sha256 checksum of a file, or other data blob\n * MD5 -- the md5 checksum of a file, or other data blob\n * SHA1 -- the sha1 checksum of a file, or other data blob\n * URL -- A minimal form of the URL\n\n The Verdict is derived from all of the Judgements on that Observable which\n have not yet expired. The highest priority Judgement becomes the\n active verdict. If there is more than one Judgement with that\n priority, than Clean disposition has priority over all others, then\n Malicious disposition, and so on down to Unknown.\n\n \u003ca href='/doc/README.md'\u003eCTIA Documentation\u003c/a\u003e","contact":{"name":"Cisco Security Business Group -- Advanced Threat ","url":"http://github.com/threatgrid/ctia","email":"cisco-intel-api-support@cisco.com"},"license":{"name":"All Rights Reserved","url":""},"version":"2.24.0"},"security":[{"oAuth2":["integration:read","private-intel:read","profile:read","inspect:read","users:read","invite:read","enrich:read","oauth:read","response:read","global-intel:read","ao:read","playbook:read"]}],"tags":[{"name":"Actor","description":"Actor operations"},{"name":"Asset","description":"Asset operations"},{"name":"Asset Mapping","description":"Asset Mapping operations"},{"name":"Asset Properties","description":"Asset Properties operations"},{"name":"Attack Pattern","description":"Attack Pattern operations"},{"name":"Campaign","description":"Campaign operations"},{"name":"Casebook","description":"Casebook operations"},{"name":"COA","description":"COA operations"},{"name":"Event","description":"Events operations"},{"name":"Feed","description":"Feed operations"},{"name":"Incident","description":"Incident operations"},{"name":"Indicator","description":"Indicator operations"},{"name":"Judgement","description":"Judgement operations"},{"name":"Malware","description":"Malware operations"},{"name":"Relationship","description":"Relationship operations"},{"name":"Sighting","description":"Sighting operations"},{"name":"Target Record","description":"Target Record operations"},{"name":"Tool","description":"Tool operations"}],"x-parser-conf":{"serverConfig":"select","overview":{"markdownPath":"reference/private-intel/overview.md","uri":"private-intel-ctia-api-guide"},"disableAuthEditing":true,"exampleAsDefault":true,"oAuth2":{"clientId":"client-546e34fc-c6bf-4951-ac69-f6d7987a7814","clientSecret":"MYw4_E_tBdFwUwrX6WFYKVD5LQrG2k7XrJ5J046wWE0s1gAKCxJ8VA","proxyEnabled":false},"meta":{"useProxy":true}},"openapi":"3.0.1","servers":[{"url":"https://private.intel.amp.cisco.com"}],"securitySchemes":{"oAuth2":{"type":"oauth2","flows":{"clientCredentials":{"tokenUrl":"https://visibility.amp.cisco.com/iroh/oauth2/token","scopes":{"telemetry":"Collect application data for analytics","integration:read":"Manage your modules","private-intel:read":"Access Private Intelligence","admin":"Provide admin privileges","cognitive":"Cognitive Integration","profile:read":"Get your profile information","inspect:read":"Extract Observables and data from text","asset":"Access and modify your assets","event":"Read IROH Events","feedback":"Submit Customer Feedback","sse":"SSE Integration. Manage your Devices.","registry":"Manage registry entries","users:read":"Manage users of your organization","investigation":"Perform threat analysis investigation","invite:read":"Invite users into your organization","casebook":"Access and modify your casebooks","playbook:read":"Access and modify your playbooks","orbital":"Orbital Integration.","enrich:read":"Query your configured modules for threat intelligence","oauth:read":"Manage OAuth2 Clients","vault":"Grants access to Module Vaults","response:read":"List and execute response actions using configured modules","notification":"Receive notifications from integrations","global-intel:read":"Access AMP Global Intelligence","webhook":"Manage your Webhooks","ao:read":"AO Integration."}}}}}},"spec":{"tags":["Vulnerability"],"summary":"Get one Vulnerability by ID","description":"Requires capability read-vulnerability.","parameters":[{"name":"id","in":"path","required":true,"schema":{"type":"string"}},{"name":"fields","in":"query","style":"form","explode":true,"schema":{"type":"array","items":{"type":"string","enum":["schema_version","revision","source","title","source_uri","language","id","tlp","timestamp"]}}}],"responses":{"200":{"description":"","content":{"application/json":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"string"}},"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"authorized_users":{"type":"array","items":{"type":"string"}},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"groups":{"type":"array","items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"},"owner":{"type":"string"}},"additionalProperties":false,"description":"Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exist in various components of the system, such as the operating system, applications, network devices, and databases.","example":{"description":"string","schema_version":"1.3.18","revision":10,"published_date":"2016-01-01T01:01:01.000Z","cve":{"cve_data_meta":{"id":"string","assigner":"string"}},"configurations":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"type":"vulnerability","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","language":"string","id":"string","tlp":"green","timestamp":"2016-01-01T01:01:01.000Z","last_modified_date":"2016-01-01T01:01:01.000Z","impact":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}}},"$$ref":"#/components/schemas/PartialVulnerability"}},"application/x-yaml":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"string"}},"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"authorized_users":{"type":"array","items":{"type":"string"}},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"groups":{"type":"array","items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"},"owner":{"type":"string"}},"additionalProperties":false,"description":"Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exist in various components of the system, such as the operating system, applications, network devices, and databases.","example":{"description":"string","schema_version":"1.3.18","revision":10,"published_date":"2016-01-01T01:01:01.000Z","cve":{"cve_data_meta":{"id":"string","assigner":"string"}},"configurations":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"type":"vulnerability","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","language":"string","id":"string","tlp":"green","timestamp":"2016-01-01T01:01:01.000Z","last_modified_date":"2016-01-01T01:01:01.000Z","impact":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}}},"$$ref":"#/components/schemas/PartialVulnerability"}},"application/edn":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"string"}},"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"authorized_users":{"type":"array","items":{"type":"string"}},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"groups":{"type":"array","items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"},"owner":{"type":"string"}},"additionalProperties":false,"description":"Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exist in various components of the system, such as the operating system, applications, network devices, and databases.","example":{"description":"string","schema_version":"1.3.18","revision":10,"published_date":"2016-01-01T01:01:01.000Z","cve":{"cve_data_meta":{"id":"string","assigner":"string"}},"configurations":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"type":"vulnerability","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","language":"string","id":"string","tlp":"green","timestamp":"2016-01-01T01:01:01.000Z","last_modified_date":"2016-01-01T01:01:01.000Z","impact":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}}},"$$ref":"#/components/schemas/PartialVulnerability"}},"application/transit+json":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"string"}},"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"authorized_users":{"type":"array","items":{"type":"string"}},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"groups":{"type":"array","items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"},"owner":{"type":"string"}},"additionalProperties":false,"description":"Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exist in various components of the system, such as the operating system, applications, network devices, and databases.","example":{"description":"string","schema_version":"1.3.18","revision":10,"published_date":"2016-01-01T01:01:01.000Z","cve":{"cve_data_meta":{"id":"string","assigner":"string"}},"configurations":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"type":"vulnerability","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","language":"string","id":"string","tlp":"green","timestamp":"2016-01-01T01:01:01.000Z","last_modified_date":"2016-01-01T01:01:01.000Z","impact":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}}},"$$ref":"#/components/schemas/PartialVulnerability"}},"application/transit+msgpack":{"schema":{"type":"object","properties":{"description":{"type":"string","description":"A description of object, which may be detailed.","example":"string"},"authorized_groups":{"type":"array","items":{"type":"string"}},"schema_version":{"type":"string"},"revision":{"type":"integer","description":"A monotonically increasing revision, incremented each time the object is changed.","format":"int64","example":10},"published_date":{"type":"string","description":"Represents the date when a vulnerability was publicly disclosed or made available to the general public. \n\nImportant for tracking the age of a vulnerability, as well as for determining when a particular vulnerability was first introduced into a system. The published date can be used to identify the time window during which a system may have been vulnerable to a particular exploit.\n\nFor example, if an organization discovers that a vulnerability was published before their system's installation date, but they did not apply the necessary security updates in a timely manner, it can be concluded that their system was vulnerable for the period between the installation date and the date when the necessary security updates were applied.","format":"date-time","example":"2016-01-01T01:01:01Z"},"cve":{"required":["cve_data_meta"],"type":"object","properties":{"cve_data_meta":{"type":"object","properties":{"id":{"type":"string","description":"String with at most 1024 characters.","example":"string"},"assigner":{"type":"string","description":"String with at most 1024 characters.","example":"string"}},"additionalProperties":false,"example":{"id":"string","assigner":"string"},"$$ref":"#/components/schemas/CVEDataMeta"}},"additionalProperties":false,"example":{"cve_data_meta":{"id":"string","assigner":"string"}},"$$ref":"#/components/schemas/CVE"},"configurations":{"required":["CVE_data_version","nodes"],"type":"object","properties":{"CVE_data_version":{"type":"string","description":"Specifies the version of the CVE (Common Vulnerabilities and Exposures) dictionary used by the vulnerability information provider.","example":"string"},"nodes":{"type":"array","description":"Each `node` in the CTIM standard configuration includes information such as the `operator` (such as \"less than\", or \"greater than or equal to\"), and the `cpe` (Common Platform Enumeration) string which identifies the specific software, `CPE` is a structured naming scheme for IT systems, platforms, and software packages, and it is instrumental in enabling data exchange between different systems.","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}],"items":{"required":["operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"children":{"type":"array","example":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"items":{"required":["cpe_match","operator"],"type":"object","properties":{"operator":{"type":"string","description":"The operator string influences how seqs of cpe matches are related to one another.","example":"AND","enum":["AND","OR"]},"cpe_match":{"type":"array","example":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"items":{"required":["cpe23Uri","vulnerable"],"type":"object","properties":{"vulnerable":{"type":"boolean","example":true},"cpe23Uri":{"type":"string","description":"A text representation of a software or hardware platform.","example":"string"},"versionStartIncluding":{"type":"string","description":"A string representing the lower bound(inclusive) of version in the CPE.","example":"string"},"versionEndIncluding":{"type":"string","description":"A string representing the upper bound(inclusive) of version in the CPE.","example":"string"},"versionStartExcluding":{"type":"string","description":"A string representing the lower bound(exclusive) of version in the CPE.","example":"string"},"versionEndExcluding":{"type":"string","description":"A string representing the upper bound(exclusive) of version in the CPE.","example":"string"}},"additionalProperties":false,"example":{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"},"$$ref":"#/components/schemas/CPEMatch"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true},"$$ref":"#/components/schemas/CPELeafNode"}},"negate":{"type":"boolean","description":"Negates operator when true.","example":true}},"additionalProperties":false,"example":{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true},"$$ref":"#/components/schemas/CPENode"}}},"additionalProperties":false,"description":"Represents a list of affected versions or configurations of a software component that is impacted by a vulnerability. \nBy tracking the affected software components and versions, defenders can identify which systems are potentially exposed to an attack, and apply appropriate mitigations.","example":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"$$ref":"#/components/schemas/Configurations"},"authorized_users":{"type":"array","items":{"type":"string"}},"type":{"type":"string","description":"The fixed value vulnerability","example":"vulnerability","enum":["vulnerability"]},"created":{"type":"string","format":"date-time"},"source":{"type":"string","description":"Represents the source of the intelligence that led to the creation of the entity.","example":"string"},"external_ids":{"type":"array","description":"It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners.","example":["string"],"items":{"type":"string"}},"modified":{"type":"string","format":"date-time"},"short_description":{"type":"string","description":"A single line, short summary of the object.","example":"string"},"title":{"type":"string","description":"A short title for this object, used as primary display and reference value.","example":"string"},"external_references":{"type":"array","description":"Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier.","example":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"items":{"required":["source_name"],"type":"object","properties":{"source_name":{"type":"string","description":"The source within which the external-reference is defined (system, registry, organization, etc.)","example":"string"},"description":{"type":"string","description":"Markdown string with at most 5000 characters.","example":"string"},"url":{"type":"string","description":"A URL reference to an external resource.","example":"string"},"hashes":{"type":"array","description":"Specifies a dictionary of hashes for the contents of the url.","example":["string"],"items":{"type":"string"}},"external_id":{"type":"string","description":"An identifier for the external reference content.","example":"string"}},"additionalProperties":false,"description":"External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.","example":{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"},"$$ref":"#/components/schemas/ExternalReference"}},"source_uri":{"type":"string","description":"URI of the source of the intelligence that led to the creation of the entity.","example":"string"},"language":{"type":"string","description":"The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.\n\nFor example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.","example":"string"},"id":{"type":"string","description":"Globally unique URI identifying this object.","example":"string"},"tlp":{"type":"string","description":"TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.\n\nIt is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.\n\nFor example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.","example":"green","enum":["white","green","red","amber"]},"client_id":{"type":"string"},"groups":{"type":"array","items":{"type":"string"}},"timestamp":{"type":"string","description":"The time this object was created at, or last modified.","format":"date-time","example":"2016-01-01T01:01:01Z"},"last_modified_date":{"type":"string","description":"Represents the date when the vulnerability metadata was last updated in the internal database.\nIt can be used to track the freshness of the vulnerability information. If the `last_modified_date` is more recent than the `published_date`, it can indicate that there has been some new information or updates related to the vulnerability, such as new patch releases or changes in the severity or impact rating.","format":"date-time","example":"2016-01-01T01:01:01Z"},"impact":{"type":"object","properties":{"cvss_v2":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. Increased integrity impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"target_distribution":{"type":"string","description":"This metric measures the proportion of vulnerable systems. It is meant as an environment-specific indicator in order to approximate the percentage of systems that could be affected by the vulnerability. The greater the proportion of vulnerable systems, the higher the score.","example":"not_defined","enum":["low","none","high","medium","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"exploitability":{"type":"string","description":"This metric measures the current state of exploit techniques or code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled thereby increasing the severity of the vulnerability.","example":"not_defined","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"access_complexity":{"type":"string","description":"This metric measures the complexity of the attack required to exploit the vulnerability once an attacker has gained access to the target system. For example, consider a buffer overflow in an Internet service: once the target system is located, the attacker can launch an exploit at will.","example":"low","enum":["low","high","medium"]},"temporal_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 temporal metrics. Temporal metrics allow analysists to calculate threat severity based on temporal factors such as reliability of vulnerability reports, availability of mitigations, and the ease or difficulty of conducting the exploit. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"user_interaction_required":{"type":"boolean","example":true},"environmental_vector_string":{"type":"string","description":"A text representation of a set of CVSSv2 environmental metrics. Environmental metrics allow analysists to calculate threat scores in relation to environmental security requirements, collateral damage potential, and target availability. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"obtain_other_privilege":{"type":"boolean","example":true},"availability_impact":{"type":"string","description":"This metric measures the impact to availability of a successfully exploited vulnerability. Availability refers to the accessibility of information resources. Attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. Increased availability impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"access_vector":{"type":"string","description":"This metric reflects how the vulnerability is exploited.The more remote an attacker can be to attack a host, the greater the vulnerability score.","example":"network","enum":["network","adjacent network","local"]},"base_severity":{"type":"string","example":"High","enum":["Medium","Info","Unknown","None","High","Low"]},"confidentiality_impact":{"type":"string","description":"This metric measures the impact on confidentiality of a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. Increasedconfidentiality impact increases the vulnerability score.","example":"complete","enum":["partial","none","complete"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]},"report_confidence":{"type":"string","description":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes, only the existence of vulnerabilities are publicized, but without specific details. The vulnerability may later be corroborated and then confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. The more a vulnerability is validated by the vendor or other reputable sources, the higher the score.","example":"not_defined","enum":["uncorroborated","unconfirmed","confirmed","not_defined"]},"authentication":{"type":"string","description":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur. The fewer authentication instances that are required, the higher the vulnerability score.","example":"none","enum":["none","single","multiple"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v2/guide","format":"double","example":10},"obtain_user_privilege":{"type":"boolean","example":true},"obtain_all_privilege":{"type":"boolean","example":true},"collateral_damage_potential":{"type":"string","description":"This metric measures the potential for loss of life or physical assets through damage or theft of property or equipment. The metric may also measure economic loss of productivity or revenue. Naturally, the greater the damage potential, the higher the vulnerability score.","example":"not_defined","enum":["low","none","high","medium_high","low_medium","not_defined"]},"remediation_level":{"type":"string","description":"The remediation level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. The less official and permanent a fix, the higher the vulnerability score is.","example":"not_defined","enum":["temporary_fix","workaround","official_fix","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv2 metrics. It is commonly used to record or transfer CVSSv2 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a users organization, measured in terms of confidentiality, integrity, and availability, That is, if an IT asset supports a business function for which availability is most important, the analyst can assign a greater value to availability, relative to confidentiality and integrity. Each security requirement has three possible values: low, medium, or high.","example":"not_defined","enum":["low","high","medium","not_defined"]}},"additionalProperties":false,"example":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"$$ref":"#/components/schemas/CVSSv2"},"cvss_v3":{"required":["base_score","base_severity","vector_string"],"type":"object","properties":{"integrity_impact":{"type":"string","description":"measures the impact to integrity of a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"modified_user_interaction":{"type":"string","description":"modified user interaction","example":"none","enum":["none","required","not_defined"]},"modified_scope":{"type":"string","description":"modified scope","example":"not_defined","enum":["changed","unchanged","not_defined"]},"availability_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"user_interaction":{"type":"string","description":"captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component","example":"none","enum":["none","required"]},"modified_integrity_impact":{"type":"string","description":"modified integrity impact","example":"not_defined","enum":["low","none","high","not_defined"]},"privileges_required":{"type":"string","description":"describes the level of privileges an attacker must possess before successfully exploiting the vulnerability","example":"high","enum":["low","none","high"]},"exploitability_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"impact_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"environmental_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"modified_availability_impact":{"type":"string","description":"modified availability impact","example":"not_defined","enum":["low","none","high","not_defined"]},"availability_impact":{"type":"string","description":"measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"scope":{"type":"string","description":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","example":"changed","enum":["changed","unchanged"]},"exploit_code_maturity":{"type":"string","description":"measures the likelihood of the vulnerability being attacked","example":"functional","enum":["high","unproven","functional","proof_of_concept","not_defined"]},"modified_attack_complexity":{"type":"string","description":"modified attack complexity","example":"not_defined","enum":["low","high","not_defined"]},"base_severity":{"type":"string","example":"critical","enum":["low","none","high","medium","critical"]},"confidentiality_impact":{"type":"string","description":"measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability","example":"high","enum":["low","none","high"]},"temporal_severity":{"type":"string","description":"temporal severity","example":"critical","enum":["low","none","high","medium","critical"]},"modified_confidentiality_impact":{"type":"string","description":"modified confidentiality impact","example":"not_defined","enum":["low","none","high","not_defined"]},"confidentiality_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"report_confidence":{"type":"string","description":"measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details","example":"confirmed","enum":["unknown","reasonable","confirmed"]},"temporal_score":{"type":"number","description":"Round up(CVSSv3BaseScore × CVSSv3ExploitCodeMaturity × CVSSv3RemediationLevel × CVSSv3ReportConfidence)","format":"double","example":10},"modified_privileges_required":{"type":"string","description":"modified privileges required","example":"not_defined","enum":["low","none","high","not_defined"]},"modified_attack_vector":{"type":"string","description":"modified attack vector","example":"not_defined","enum":["network","adjacent_network","local","physical","not_defined"]},"base_score":{"type":"number","description":"The base score is a key metric in CVSS, which uses a scoring system to determine the level of severity of a vulnerability. see: https://www.first.org/cvss/v3-1","format":"double","example":10},"environmental_score":{"type":"number","description":"a Score number from 0 to 10","format":"double","example":10},"remediation_level":{"type":"string","description":"Remediation Level of a vulnerability is an important factor for prioritization","example":"high","enum":["temporary_fix","offical_fix","high","workaround","unavailable","not_defined"]},"vector_string":{"type":"string","description":"a text representation of a set of CVSSv3 metrics. It is commonly used to record or transfer CVSSv3 metric information in a concise form","example":"string"},"integrity_requirement":{"type":"string","description":"These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user's organization, measured in terms of Confidentiality, Integrity, and Availability. That is, if an IT asset supports a business function for which Availability is most important, the analyst can assign a greater value to Availability relative to Confidentiality and Integrity. Each security requirement has three possible values: Low, Medium, or High. The full effect on the environmental score is determined by the corresponding Modified Base Impact metrics. That is, these metrics modify the environmental score by reweighting the Modified Confidentiality, Integrity, and Availability impact metrics. For example, the Modified Confidentialityimpact (MC) metric has increased weight if the Confidentiality Requirement (CR) is High. Likewise, the Modified Confidentiality impact metric has decreased weight if the Confidentiality Requirement is Low. The Modified Confidentiality impact metric weighting is neutral if the Confidentiality Requirement is Medium. This same process is applied to the Integrity and Availability requirements.Note that the Confidentiality Requirement will not affect the Environmental score if the (Modified Base) confidentiality impact is set to None. Also, increasing the Confidentiality Requirement from Medium to Highwill not change the Environmental score when the (Modified Base) impact metrics are set to High. This is because the modified impact sub score (part of the Modified Base score that calculates impact) is already at a maximum value of 10. The list of possible values is: `not_defined`: Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. `high`: Loss of [Confidentiality / Integrity / Availability] is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). `medium`: Loss of [Confidentiality / Integrity / Availability] is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).`low`: Loss of [Confidentiality / Integrity / Availability] is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers). For brevity, the same table is used for all three metrics. The greater the Security Requirement, the higher the score (recall that Medium is considered the default).","example":"high","enum":["low","none","high","not_defined"]},"attack_vector":{"type":"string","description":"Reflects the context by which vulnerability exploitation is possible","example":"adjacent_network","enum":["network","adjacent_network","local","physical"]},"attack_complexity":{"type":"string","description":"describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability","example":"high","enum":["low","high"]}},"additionalProperties":false,"example":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"},"$$ref":"#/components/schemas/CVSSv3"}},"additionalProperties":false,"description":"Describes the potential impact of a vulnerability that is being tracked in the system. Provides information on the extent of damage that a vulnerability can cause and how serious the consequences could be if it is exploited. \n\nMay contain granular information about the vulnerability severity using the CVSS system, versions 2 and 3.\n\nCVSSv2 and CVSSv3 have different methods of calculating base scores, but both are designed to provide an indication of the level of risk that a vulnerability poses. The base score ranges from 0 to 10, with 10 being the most severe. Additionally, both CVSSv2 and CVSSv3 define severity levels, such as low, medium, high, and critical, based on the base score.","example":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}},"$$ref":"#/components/schemas/VulnerabilityImpact"},"owner":{"type":"string"}},"additionalProperties":false,"description":"Indicates weakness or flaw in the system that can be exploited by an attacker to gain unauthorized access or cause harm to the system. Vulnerabilities can exist in various components of the system, such as the operating system, applications, network devices, and databases.","example":{"description":"string","schema_version":"1.3.18","revision":10,"published_date":"2016-01-01T01:01:01.000Z","cve":{"cve_data_meta":{"id":"string","assigner":"string"}},"configurations":{"CVE_data_version":"string","nodes":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"children":[{"operator":"AND","cpe_match":[{"vulnerable":true,"cpe23Uri":"string","versionStartIncluding":"string","versionEndIncluding":"string","versionStartExcluding":"string","versionEndExcluding":"string"}],"negate":true}],"negate":true}]},"type":"vulnerability","source":"string","external_ids":["string"],"short_description":"string","title":"string","external_references":[{"source_name":"string","description":"string","url":"string","hashes":["string"],"external_id":"string"}],"source_uri":"string","language":"string","id":"string","tlp":"green","timestamp":"2016-01-01T01:01:01.000Z","last_modified_date":"2016-01-01T01:01:01.000Z","impact":{"cvss_v2":{"integrity_impact":"complete","target_distribution":"not_defined","availability_requirement":"not_defined","exploitability":"not_defined","access_complexity":"low","temporal_vector_string":"string","exploitability_score":10,"impact_score":10,"user_interaction_required":true,"environmental_vector_string":"string","obtain_other_privilege":true,"availability_impact":"complete","access_vector":"network","base_severity":"High","confidentiality_impact":"complete","confidentiality_requirement":"not_defined","report_confidence":"not_defined","authentication":"none","base_score":10,"obtain_user_privilege":true,"obtain_all_privilege":true,"collateral_damage_potential":"not_defined","remediation_level":"not_defined","vector_string":"string","integrity_requirement":"not_defined"},"cvss_v3":{"integrity_impact":"high","modified_user_interaction":"none","modified_scope":"not_defined","availability_requirement":"high","user_interaction":"none","modified_integrity_impact":"not_defined","privileges_required":"high","exploitability_score":10,"impact_score":10,"environmental_severity":"critical","modified_availability_impact":"not_defined","availability_impact":"high","scope":"changed","exploit_code_maturity":"functional","modified_attack_complexity":"not_defined","base_severity":"critical","confidentiality_impact":"high","temporal_severity":"critical","modified_confidentiality_impact":"not_defined","confidentiality_requirement":"high","report_confidence":"confirmed","temporal_score":10,"modified_privileges_required":"not_defined","modified_attack_vector":"not_defined","base_score":10,"environmental_score":10,"remediation_level":"high","vector_string":"string","integrity_requirement":"high","attack_vector":"adjacent_network","attack_complexity":"high"}}},"$$ref":"#/components/schemas/PartialVulnerability"}}}}},"security":[{"oAuth2":["integration:read","private-intel:read","profile:read","inspect:read","users:read","invite:read","enrich:read","oauth:read","response:read","global-intel:read","ao:read","playbook:read"]}],"method":"get","path":"/ctia/vulnerability/{id}"}}