Vulnerability Exposure Index (VEX) Database

Link to article: Vulnerability Exposure Index (VEX) Database.


th {
   border: 2px solid rgb(var(--accent-color));
   background-color: rgb(var(--accent-color));
   color: rgb(var(--pitch-black));
   padding: 0.5rem;
    white-space: nowrap;
    width: 0.01%;
}

td {
   border: 2px solid rgb(var(--dark-midnight));
   background-color: rgb(var(--dark-midnight));
   padding: 0.5rem;
}

span.green {
   color: rgb(var(--mutant-green));
   font-weight: bold;
}

span.blue {
   color: rgb(var(--skylight-blue));
   font-weight: bold;
}

span.violet {
   color: rgb(var(--lavender-violet));
   font-weight: bold;
} 

span.orange {
   color: rgb(var(--neon-orange));
   font-weight: bold;
}

span.red {
   color: rgb(var(--deep-crimson));
   font-weight: bold;
}

.footnotes-footer {
display: none;
}

margin-bottom: unset; border-bottom-left-radius: 0; border-bottom-right-radius: 0; padding: 15px 15px 0px 15px;

padding-top: .15rem; padding-bottom: .15rem;

```
color: rgb(var(--accent-color));
```

background-color: rgb(var(--accent-color)); border-color: rgb(var(--accent-color)); color: rgb(var(--pitch-black)); margin-top: 0px; padding-top: 0px; padding-bottom: 0px; line-height: 19px; border-top-left-radius: 0; border-top-right-radius: 0;

font-weight: bold;color: rgb(var(--accent-color));

font-weight: bold;color: rgb(var(--mutant-green));

font-weight: bold;color: rgb(var(--skylight-blue));

font-weight: bold;color: rgb(var(--neon-orange));

font-weight: bold;color: rgb(var(--deep-crimson));

font-weight: bold;color: rgb(var(--accent-color));

font-weight: bold;color: rgb(var(--mutant-green));

font-weight: bold;color: rgb(var(--skylight-blue));

font-weight: bold;color: rgb(var(--neon-orange));

font-weight: bold;color: rgb(var(--deep-crimson));

font-weight: bold;color: rgb(var(--accent-color));

font-weight: bold;color: rgb(var(--mutant-green));

font-weight: bold;color: rgb(var(--skylight-blue));

font-weight: bold;color: rgb(var(--neon-orange));

font-weight: bold;color: rgb(var(--deep-crimson));

font-weight: bold;color: rgb(var(--skylight-blue));

font-weight: bold;color: rgb(var(--neon-orange));

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;

```
text-align: center;
```

text-align: center; font-weight: bold; color: rgb(var(--accent-color));

```
font-weight: bold; text-align: center;
```
```
text-align: center; font-weight: bold;
```
```
text-align: center;
```

```
modal
```
```
expoblock
```
```
modal
```
```
hilighter
```
```
hilighter
```
```
hilighter
```
```
hilighter
```
```
hilighter
```
```
orange
```
```
green
```
```
green
```
```
red
```
```
blue
```
```
green
```
```
green
```
```
blue
```
```
blue
```
```
blue
```
```
blue
```
```
blue
```
```
green
```
```
green
```
```
blue
```
```
red
```
```
green
```
```
green
```
```
orange
```
```
red
```
```
blue
```
```
blue
```
```
orange
```
```
green
```
```
blue
```
```
red
```
```
orange
```
```
green
```
```
red
```
```
red
```
```
red
```
```
red
```
```
red/blue/orange/green/purple
```
```
red/blue/orange/green/purple
```
```
red/blue/orange/green/purple
```
```
violet
```
```
green
```
```
blue
```
```
orange
```
```
red
```
```
red
```
```
red
```
```
blue
```
```
blue
```

[[include :scp-wiki:theme:black-highlighter-theme]]
[[include :scp-wiki:theme:new-age violet=a | hidetitle=a]]
[[=]]
[[module Rate]]
[[/=]]
[[div class="modal" style="margin-bottom: unset; border-bottom-left-radius: 0; border-bottom-right-radius: 0; padding: 15px 15px 0px 15px;"]]
[[div class="expoblock" style="padding-top: .15rem; padding-bottom: .15rem;"]]
{{##grey|Type here to search all available records...##}}
[[/div]]
= [[size 85%]]{{**[[span style="color: rgb(var(--accent-color));"]]18,452[[/span]]** VEX records have been documented by **[[[/simulacrum-project-hub|SIMULACRUM]]]** authorities.}}[[/size]]
[[/div]]
[[div class="modal" style="background-color: rgb(var(--accent-color)); border-color: rgb(var(--accent-color)); color: rgb(var(--pitch-black)); margin-top: 0px; padding-top: 0px; padding-bottom: 0px; line-height: 19px; border-top-left-radius: 0; border-top-right-radius: 0;"]]
[[size 90%]]**ⓘ Unsure how to continue? Refer below for further information.**[[/size]] 
[[/div]]
@@ @@
+ OVERVIEW
----
Security is crucial to Project **SIMULACRUM**'s continued success. The [[span class="hilighter"]]Vulnerability Exposure Index (VEX)[[/span]] database provides a centralized catalogue for disclosing and documenting known threats to **SIMULACRUM**'s environment, inhabitants, items, virtual sandboxes, and external infrastructure. VEX records are enumerated by their entry IDs (VEX-YYYY-NNN) which documents the year that the identified vulnerability was discovered in and a unique sequence numerical for categorization. 

[[=]]
[[collapsible show="Click here for more information..." hide="Click here to hide information..." hideLocation="bottom"]]
[[<]]

VEX records provide in-depth information regarding specific vulnerabilities. This includes a description, impact, status, severity, related item(s), assigned authorities, mitigation procedures, and any repercussions determined to be directly or indirectly caused by the threat itself. All records are appropriately color-coded based on severity. 

[[span class="hilighter"]]Severity[[/span]] indicates the perceived risk that a vulnerability possesses if left unmitigated. This metric is assessed by a numerical scale ranging from [[span style="font-weight: bold;color: rgb(var(--accent-color));"]]0.0[[/span]] (Informational) to [[span style="font-weight: bold;color: rgb(var(--mutant-green));"]]0.1 - 2.5[[/span]] (Low), [[span style="font-weight: bold;color: rgb(var(--skylight-blue));"]]2.6 - 5.0[[/span]] (Medium), [[span style="font-weight: bold;color: rgb(var(--neon-orange));"]]5.1 - 7.5[[/span]] (High), or [[span style="font-weight: bold;color: rgb(var(--deep-crimson));"]]7.6 - 10.0[[/span]] (Critical). Severity does not always suggest that an unmitigated threat will have widespread effects; rather it indicates the perceived damage that it can potentially cause overall.

To determine the scale at which a vulnerability can affect multiple systems or users, VEX records document a vulnerability's [[span class="hilighter"]]Impact[[/span]]. Impact is measured as [[span style="font-weight: bold;color: rgb(var(--accent-color));"]]MINIMAL[[/span]], [[span style="font-weight: bold;color: rgb(var(--mutant-green));"]]LOW[[/span]], [[span style="font-weight: bold;color: rgb(var(--skylight-blue));"]]MEDIUM[[/span]], [[span style="font-weight: bold;color: rgb(var(--neon-orange));"]]HIGH[[/span]], or [[span style="font-weight: bold;color: rgb(var(--deep-crimson));"]]CRITICAL[[/span]], depending on the number of items (if any) that may be affected by a specific threat. Impact assessments are not all inclusive, and may incorporate additional considerations such as **SIMULACRUM** sandbox size, Site structure, player capacity, or [[[/scp-4523|physical resource utilization]]].

In order to assist operators and personnel utilizing this database, VEX records will also display the last known [[span class="hilighter"]]Status[[/span]] of a vulnerability. Status documents whether a vulnerability is [[span style="font-weight: bold;color: rgb(var(--accent-color));"]]PENDING[[/span]], [[span style="font-weight: bold;color: rgb(var(--mutant-green));"]]ERADICATED[[/span]], [[span style="font-weight: bold;color: rgb(var(--skylight-blue));"]]REMEDIED[[/span]], [[span style="font-weight: bold;color: rgb(var(--neon-orange));"]]ACTIVE[[/span]], or [[span style="font-weight: bold;color: rgb(var(--deep-crimson));"]]FUTILE[[/span]]. As status only reflects a vulnerability's last known activity, any outstanding impact or repercussions caused by a particular threat are not considered in this metric.[[footnote]]For example, a successfully executed malware signature that was quarantined and [[span style="font-weight: bold;color: rgb(var(--skylight-blue));"]]REMEDIED[[/span]] by intrusion prevention systems (IPSs) would not be considered [[span style="font-weight: bold;color: rgb(var(--neon-orange));"]]ACTIVE[[/span]] even if impacted data or systems are still currently affected.[[/footnote]] 

Individual VEX records are documented and supported by an assigned [[span class="hilighter"]]Authority[[/span]]. Authorities can be comprised of **SIMULACRUM** operators, administrators, or other third-party organizations and Groups of Interest (GoI). Assigned authorities are responsible for reporting, and classifying cyberanomalous threats as they manifest. Multiple authorities may also collaborate together in order to properly document discovered vulnerabilities, improve relations, and/or enhance cooperation efforts made between other virtualized or physical parties. Utilize the above search function to locate particular VEX records, or refer below to several of the most recently submitted entries.
[[/<]]
[[/collapsible]]
[[/=]]
@@ @@
+ RECENT RECORDS
----
[[div class="orange"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-2045-003
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
7.4
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* [[[SCP-6882]]]
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:** 
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Improper access controls across **SIMULACRUM** meshlayer firmware versions would allow affected players to bypass predefined world boundaries. This, in essence, allowed for uninterrupted access to any bordering sandboxes.

In some versions, players were not only able to bypass these borders, but could also access edit parameters within their sandbox, thus granting them access to elevated administrator commands.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Simulations bordering vulnerable sandboxes were mostly reserved for testing and containment of undocumented large-scale virtual aggressors (LSVAs) or other unknown anomalous phenomenon. Players exploiting this vulnerability could disrupt these simulations through physical interaction or by executing elevated commands.

Players with internal system access to their own sandboxes could also "piggyback" off their instances and into other remote sandboxes. In one case, several unknown attackers were able to sabotage the SCP-6882 virtual instance and hijack its noospheric platform interface, causing connected players to undergo rapid mental and physical deterioration before an unexpected sandbox crash later occured.

Attackers were able to successfully input coordinate commands to bypass detection; however, improper values resulted in threat actors falling out-of-bounds and missing subsequent bound checks. Recovery efforts have been futile. 
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Firmware updates are available for all affected virtual sandboxes. Complete system restart is necessary to apply changes. Additional vendor-specific hotfix patches have been successfully deployed across all platforms and unattached virtual instances.
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="green"]]ERADICATED[[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="green"]]Low[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
[[[/scp-7766|Dr. Jakob Reigen]]]
[[/cell]]
[[/row]]
[[/table]]
[[/div]]

[[div class="red"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-2032-682
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
9.8
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* **[[span class="blue"]][[[/scp-5242|SCP-INTEGER]]][[/span]]**
* [[span class="green"]]MAKER[[/span]]
* SIMULA-9025-1B
* SIMULA-7621-3C
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Unsecured data root paths between sandboxes from the **[[span class="green"]][[[/scp-7346|PRIME INDEX]]][[/span]]** could allow [[[/domc-hub|semiohazardous]]] phenomenon to affect multiple **SIMULACRUM** layers.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Disaster recovery systems flagged and restored a cascading network file system crash after a failed interaction between two sandboxes. Prior to the alerted incident, SIMULA-9025-1B -- an abstracted reality intended to test interactions between [[[/scp-5795|ontokinetic]]], semiohazardous, and other reality-altering anomalies -- had initiated a resource request from SIMULA-7621-3C.

During the response operation by SIMULA-7621-3C, an undetected [[span class="blue"]]HAZARD[[/span]] was also transferred. This [[span class="blue"]]COMPLEX[[/span]] was then successfully executed after both sandboxes confirmed its presence and attempted to forcibly delete the [[span class="blue"]]THREAT[[/span]]. Due to outdated data signatures, the [[span class="blue"]]HAZARD[[/span]] began systematically updating all reference pointers, files, and datasets with abstractions, halting system functions across 3,451 connected instances.

[[span class="blue"]]COMPLEX[[/span]] manifested itself within SIMULA-9025-1B, alerting host player [[span class="green"]]MAKER[[/span]]. Attempts by [[span class="green"]]MAKER[[/span]] to notify **SIMULACRUM** administrators of the [[span class="blue"]]MALWARE[[/span]][[footnote]][[span class="red"]]SLANDER[[/span]].[[/footnote]] subsequently failed as null counters disrupted operations. Automated systems were unable to fully repair either sandboxes or regenerate [[span class="green"]]MAKER[[/span]] from backup player matrices. 
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Standard requests sent by client and serving sandboxes have been updated to introduce an additional CHECK flag to determine if data being sent or received contains anomalous traces. Host-based detection/removal systems have also been updated across all active **SIMULACRUM** instances to cleanse deployments of potential reality-altering hazards. 

[[span class="green"]]PRIME INDEX[[/span]] roots have been updated to utilize the latest security protocols. Improved pathing methods between sandboxes have also been introduced to now disconnect instances determined to be at risk of anomalous leakage. 

**SIMULACRUM** authorities have all received additional training on dealing with active cognitive hazards, including semiohazardous and infohazardous phenomenon.
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="orange"]]ACTIVE[[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="red"]]CRITICAL[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
Dr. Devin Collins
[[/cell]]
[[/row]]
[[/table]]
[[/div]]

[[div class="blue"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-2423-019
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
4.8
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* [[[SCP-6872]]]
* [[[SCP-2718]]]
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:** 
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
A buffer overflow in the {{commit_action}} module in SCP-6872 would incorrectly reference SCP-2718, resulting in multiple errors and extraordinary physical harm onto players. Continued conflicts could cause a denial of service (crash) and possibly execute additional root-level commands.

In some instances, players experiencing multiple requests between both SCP-6872 and SCP-2718 could also be afflicted by both conditions simultaneously, leading to corrupted reference caches and other errors. 
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
During the rapid deployment of sub-simulations within SCP-6872, an increased strain on incoming state requests resulted in players being incorrectly assigned to SCP-2718. During this period, players experiencing the "DECEASED" state would not be transported to their simulated death sequences-- rather, affected individuals would either be terminated from their hosting simulation entirely or remain permanently immobile and unable to disconnect from their sessions. This resulted in players being in multiple states of "DECEASED" between several sandboxes.

In other circumstances, physical players would be completely ejected from all sandboxes. Excessive electric discharge caused by the vulnerability sent uncontrolled shocks through sensitive neural interfaces, physically disabling players and locking their player pods indefinitely. Players would still report active heartbeats despite being clinically deceased, bypassing all system monitoring tools for extended periods of time. This resulted in player pods being contaminated with excess organisms, including bacteria, mites, mold, and flies.

All later attempts to remove players from their pods universally ended in failure.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Additional software-level checks against possible overflows have been implemented to prevent any issues with SCP-6872 and SCP-2718. Additional system monitoring tools have been implemented to confirm player status through haptic and audio feedback. All active neural network interfaces have also been issued a firmware update and all player pods have been refitted with emergency release latches.
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="blue"]]REMEDIED[[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="orange"]]Medium[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
**{{[AUTOMATED]}}**
[[/cell]]
[[/row]]
[[/table]]
[[/div]]



[[div class="green"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-2076-303
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
1.7
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* SIMULA-Y200-2K
* {{cron}} version 23
* Docker version 1001001010001.3
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
On Docker versions that form a valid number string in binary, {{cron}} would read it as a valid character string instead. This would cause various issues, including system failure.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
SIMULA-Y200-2K is a sandboxed reality designed to output a single value -- the default system time of baseline reality pre-**SIMULACRUM.** This is done to maintain legacy systems that expect a standard time on certain functions instead of the advanced system time of IEEE 4098.32, the standardized **SIMULACRUM** timestamp. 

Retrieval of the legacy system timestamp is done through a {{cron}} script, which first checks for the current Docker version, and only fetches a new system timestamp if the version number had recently changed. Due to issues with {{cron}}, Docker version number strings would sometimes be misinterpreted as invalid character strings when updated.

Because of this, severe momentary failure for all SIMULA instances that depended on the legacy system time occurred. As of 2075, 321 SIMULA instances were dependent on legacy timestamps, subsequently leading to indirect system failures of those sandboxes and 8,321,098,321 other connected dependencies.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
A patch to {{cron}}'s developer has been sent to disable interpretation of binary strings as regular characters. System administrators are currently collaborating with Docker to ensure that no version number is an interpretable character string.
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="blue"]]REMEDIED[[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="red"]]CRITICAL[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
Dr. Basir
[[/cell]]
[[/row]]
[[/table]]
[[/div]]

[[div class="orange"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-2099-002
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
7.2
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* [[[SCP-8155]]]
* Neurological Maternal Decay Syndrome
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:** 
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
A collection of five unaccounted glitches manifesting over the course of two months that were able to successfully severely damage the hosted mainframe via the use of --9-- 16 server crashes.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
In the immediate culmination of SCP-8155 via all five glitches resulted in a severe malfunction within SIMULA-2099-02 manifesting as an account of a en masse ontological breakdown as well as all female **SIMULACRUM** participants to contract a supreme version of "Maternal Decay Syndrome," a **SIMULACRUM** virus acting as a neurological memetic impairment that ceased all female inhabitants abilities to reproduce, reciprocate love for their young, as well as a deconstruction and destruction of all familial conceptual base components implemented into the  **SIMULACRUM** server. 
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Attempts to derail the situation via repairs to the mainframe were attempted by VEX-2196-002. Initial attempts were futile, however over the course of multiple server restarts, 2196-002 were successful in mitigating the threat posed by SCP-8155, albeit with significant financial and mental costs that resulted in the derealization of their participation within all SCP Foundation-acting parties, most likely due to an error in the management of VEX-2099-002.

Mitigation was deemed successful, however, the actual nature as well as origins of how SCP-8155 was able to impact the vex server mainframe's on such a large and impactful basis is unknown and currently being extensively investigated.
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="green"]]ERADICATED[[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="red"]]HIGH[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
[[[/scp-7793|Dr. Christopher Blashman]]]
[[/cell]]
[[/row]]
[[/table]]
[[/div]]

[[div class="red"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-2330-031
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
10 
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* [[[SCP-3031]]]
* [[[SCP-7371]]]
* [[[SCP-8008]]]
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Site-119's Extra-Temporal/Reality Receiver which provides reference data to SIMULACRUM technology and establishes causal loops to ensure their functionality, has repeatedly malfunctioned during relevant operations. RCT-Δt has traced this to the combined influence of SCP-7371 and SCP-8008, as the ET/RR was used by the Historical Continuity Division and American Secure Containment Initiative to combat the former and is a prime target of the latter due to modifications of SCP-3031 used in it's containment.

Available data suggests an additional party orchestrating and maintaining this activity, but further details on the subject have been difficult to verify.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Large sums of data within the SIMULACRUM infrastructure have been lost to causal disruptions, separated from conceivable reality. Furthermore, said informational disruptions have a cascading effect on all connected systems, corrupting data within to produce various aberrations. These distortions affect human biology due to the operations involved, expanding its influence throughout history.

All factors involved form a causal loop that allows distortions to impact SIMULACRUM and connected networks. Consequently, the information involved is totally isolated from external reality and retroactively prevents interactions with it throughout history.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
No proper mitigation has been developed at the time of writing. Backups of SIMULACRUM data have been distributed throughout various timelines to reduce associated damages. RCT-Δt's Temporal Intelligence Community has been tasked with identifying any relevant data on the subject of the threat. 
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="red"]]FUTILE [[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="red"]]CRITICAL[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
Dir. Jakobi Carmen
[[/cell]]
[[/row]]
[[/table]]
[[/div]]

@@ @@
+ CONTRIBUTION
----
@@ @@
Contributions can be made using the following VEX record format:

[[=]]
[[collapsible show="Click here to view VEX format template..." hide="Click here to close VEX format template..." hideLocation="bottom"]]
[[<]]
[[code type="css"]]

[[div class="red/blue/orange/green/purple"]]
[[table style="width: 100%; border-collapse:collapse; margin-top: 2.5rem; margin-bottom: 2.5rem;"]]
[[row]]
[[hcell]]
**VEX ID:**
[[/hcell]]
[[cell colspan="3" style="text-align: center;"]]
VEX-YYYY-NNN
[[/cell]]
[[hcell]]
**SEVERITY:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold; color: rgb(var(--accent-color));"]]
Severity should be placed here. Be sure that the color of the table matches the value range of the severity. (0 should be purple, 0.1 - 2.5 should be green, 2.5 - 5 should be blue, 5 - 7.5 should be orange, and 7.5 to 10 should red)
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**RELATED ITEMS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
* A list of anomalies or systems relating to, or directly caused by the vulnerability should be placed here.
* Add as many items as needed here.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**DESCRIPTION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Information describing what the actual vulnerability is should go here. Refrain from adding too much information regarding other systems or processes. This field should be solely reserved for documenting what the vulnerability is and how it operates.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**REPERCUSSIONS:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Information describing the effects of the described vulnerability should go here. This field can be used to document the systems responsible for the vulnerability, events which happened as a direct or indirect result of the vulnerability, or any other pertinent details.
[[/cell]]
[[/row]]
[[row]]
[[hcell colspan="6"]]
**MITIGATION:**
[[/hcell]]
[[/row]]
[[row]]
[[cell colspan="6"]]
Information involving how to mitigate the described vulnerability should go here. Be descriptive regarding the steps or actions required to be taken to prevent further issues or exploitation.
[[/cell]]
[[/row]]
[[row]]
[[hcell]]
**STATUS:**
[[/hcell]]
[[cell style="font-weight: bold; text-align: center;"]]
[[span class="red/blue/orange/green/purple"]]STATUS HERE (PENDING/ERADICATED/REMEDIED/INACTIVE/ACTIVE/FUTILE)[/span]]
[[/cell]]
[[hcell]]
**IMPACT:**
[[/hcell]]
[[cell style="text-align: center; font-weight: bold;"]]
[[span class="red/blue/orange/green/purple"]]IMPACT HERE (MINIMAL/LOW/MEDIUM/HIGH/CRITICAL)[[/span]]
[[/cell]]
[[hcell]]
**AUTHORITY:**
[[/hcell]]
[[cell style="text-align: center;"]]
The individual or group responsible for documenting this vulnerabilty goes here. This will most likely be a researcher, doctor, or Foundation agent who takes responsibility for this record.
[[/cell]]
[[/row]]
[[/table]]
[[/div]]

[[/code]]
[[/<]]
[[/collapsible]]
[[/=]]

Note that only a single color ([[span class="violet"]]VIOLET[[/span]], [[span class="green"]]GREEN[[/span]], [[span class="blue"]]BLUE[[/span]], [[span class="orange"]]ORANGE[[/span]], or [[span class="red"]]RED[[/span]]) should be selected when using a {{[[div]]}} or {{@@[[span]]@@}}, if required. For example, in order to properly display a colored word like [[span class="red"]]FUTILE[[/span]], please use the following formatting: 
> {{@@[[span class="red"]]FUTILE[[/span]]@@}}
Alternatively, if a VEX record needs to be [[span class="blue"]]BLUE[[/span]], please encapsulate your VEX record table with the following syntax:
> {{@@[[div class="blue"]]@@}}
> {{...}}
> {{@@[[/div]]@@}}
Upon documenting a VEX record, please be sure to verify that all of the formatting is correct and accurate. If there are no issues, a new VEX record should populate in the Recent Records section.

[[=]]
[[include :scp-wiki:component:license-box
|author=JakdragonX and basirskipreader]]
[[include :scp-wiki:component:license-box-end]]
[[/=]]





[[module CSS]]

th {
   border: 2px solid rgb(var(--accent-color));
   background-color: rgb(var(--accent-color));
   color: rgb(var(--pitch-black));
   padding: 0.5rem;
    white-space: nowrap;
    width: 0.01%;
}

td {
   border: 2px solid rgb(var(--dark-midnight));
   background-color: rgb(var(--dark-midnight));
   padding: 0.5rem;
}

span.green {
   color: rgb(var(--mutant-green));
   font-weight: bold;
}

span.blue {
   color: rgb(var(--skylight-blue));
   font-weight: bold;
}

span.violet {
   color: rgb(var(--lavender-violet));
   font-weight: bold;
} 

span.orange {
   color: rgb(var(--neon-orange));
   font-weight: bold;
}

span.red {
   color: rgb(var(--deep-crimson));
   font-weight: bold;
}

.footnotes-footer {
display: none;
}
[[/module]]

Vulnerability Exposure Index (VEX) Database

Module Styles

Inline Styles

Includes

CSS Classes

Page Source