How this simulation works
- Read the scenario, then open each exhibit tab. Use the evidence to complete the tasks.
- Select Submit answers when you finish. Each correct matching row or ordering position earns one point. For multiple-selection tasks, each correct selection earns one point and each incorrect selection subtracts one point, with a minimum of zero for that task.
- After submission, review the correct answers and explanations. Select Reset simulation to clear answers, feedback, tools, and the timer.
- The pacing timer is optional. You can inspect every exhibit after submitting. Practice scores use this activity's rubric.
CS0-004 objectives practiced:
- 2.2 Interpret vulnerability-assessment output
- 2.3 Use vulnerability data and context to prioritize remediation
All organizations, people, events, findings, and tool records in this activity are fictional. External addresses use documentation IP ranges and reserved .example names. Commands and network records are displayed as text only. The activity runs locally, saves no student data, and makes no network requests. Reference links open only when selected. This is practice and is not graded.
Pacing timer
Scenario
The Tamberlin vulnerability team has four findings and one immediate production change window. Interpret the supplied CVSS v3.1 vectors, validate a banner-based finding, and select the work that meets the organization’s emergency policy.
Use the reference exhibit when needed. You do not need to calculate a CVSS score by hand.
Exhibits
- All THN-V identifiers name fictional findings, not published vulnerability identifiers. The example advisory and package versions belong only to this case.
- Emergency (48 hours): a validated finding has confirmed active exploitation against the organization, or an internet-facing asset has a base score of at least 9.0.
- Standard (30 days): any other validated finding with an available fix. An isolated test system remains in scope for remediation.
- False positive: evidence confirms the reported weakness is absent. Document validation before closing the finding.
- The current production change window can address one finding immediately. Use the stated emergency criteria to select it. Available patches have passed the required compatibility tests.
- This activity uses Common Vulnerability Scoring System (CVSS) v3.1 throughout. Its base score describes a weakness’s technical severity. The organization combines that information with exposure, business use, and exploitation evidence to decide work order.
Scanner findings and supplied base scores
| Finding | Asset / finding | CVSS v3.1 vector | Base score | Operational context |
|---|---|---|---|---|
| THN-V01 | test-render01: remote code execution in a rendering service | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | 9.8 | Isolated test network; synthetic data only; no route from production or internet; no exploitation observed; fix available. |
| THN-V02 | portal-app01: authenticated remote code execution | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | 8.8 | Internet-facing patient portal; existing low-privilege account required; incident team confirmed exploitation against this asset; fix available. |
| THN-V03 | 60 clinic workstations: local privilege escalation | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | 7.8 | Requires local low-privilege access; no observed exploitation; vendor patch available. |
| THN-V04 | intranet-web02: reflected cross-site scripting (XSS) | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | 6.1 | Banner-based detection. Review the package and advisory exhibit before deciding whether the finding is valid. XSS can make a user’s browser run injected script. |
Validation records for THN-V04
| Record | Evidence |
|---|---|
| S01: scanner method | Unauthenticated banner check. Banner reported THN Web 2.4.8. The plugin flagged all upstream versions before 2.4.9. No behavior test was performed. |
| V01: fictional vendor advisory | The vendor backported the XSS fix into package 2.4.8-thn6. Revision thn6 and later include the fix while the service banner still reports 2.4.8. |
| H01: authenticated host inventory | Installed package is 2.4.8-thn6. Package integrity validation passes. The service was restarted after installation and its running executable matches this package. |
| V02: original vulnerability description | Before the fix, an attacker needed no account. A victim had to open a crafted link. Successful exploitation affected the victim browser under a different security authority, with limited confidentiality and integrity impact and no availability impact. |
A backport applies a security fix to an older maintained software branch. The original CVSS vector describes the unpatched weakness. Validation determines whether that weakness exists in the installed system.
CVSS v3.1 metric reference
| Metric | Values / meaning |
|---|---|
| AV: Attack Vector | N network; A adjacent; L local; P physical. Describes the access path required for exploitation. |
| AC: Attack Complexity | L low; H high. High requires conditions beyond the attacker’s control. |
| PR: Privileges Required | N none; L low; H high. Describes privileges needed before exploitation. |
| UI: User Interaction | N none; R required. Refers to participation by another user. |
| S: Scope | U unchanged; C changed. Changed means impact crosses the vulnerable component’s security authority. |
| C / I / A: Confidentiality / Integrity / Availability | N none; L low; H high. Describes impact on disclosure, unauthorized modification, and access to service. |
| Qualitative severity | None 0.0; Low 0.1–3.9; Medium 4.0–6.9; High 7.0–8.9; Critical 9.0–10.0. |
A vector records metric choices. Scores in this activity are supplied so you can focus on interpretation. Base metrics describe inherent properties. Temporal metrics address changing factors such as exploit maturity and fixes. Environmental metrics adapt the assessment to an organization’s setting.
Tasks
Task 1 (8 points)
Task 2 (4 points)
Task 3 (1 point)
Task 4 (1 point)
Task 5 (1 point)
Task 6 (1 point)
Reference links and simulation notes
These sources support the technical concepts. All case evidence was written for this practice activity. No external source is required to answer the tasks.
- CompTIA CS0-004 exam objectives (opens a new tab)
- FIRST: CVSS v3.1 specification (opens a new tab)
- FIRST: CVSS v3.1 user guide (opens a new tab)
- FIRST: CVSS v3.1 calculator (opens a new tab)
The four base scores were independently recalculated from the supplied vectors using the CVSS v3.1 base equations. No v4.0 metrics or scores appear in this activity.