Big Rivers Ltd Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-01 | Presenter: Chris Knospe | Export set: 10 in export (Top 10) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Firebird 2.5.2.26539 (Win32) Remediation Options: Update to version 3.0.10 or later; uninstall if not in use Target Machines: Leo-Mini.BRLSERVER (lpinto) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: idrac Remediation Options: Update firmware to the current vendor release, or replace the device if it is out of support Target Machines: idrac Estimated Time of Remediation: 1 hour Remediation Method: Update firmware from the vendor during a maintenance window. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Reader XI (11.0.23) Remediation Options: Update to version 11.0.2 or later; uninstall if not in use Target Machines: Leo-Mini.BRLSERVER (lpinto) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 2.5 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top Ten vulnerabilities docx report - Ticket #1902028: Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade) - Ticket #1902029: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1902030: Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required - Ticket #1902031: Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required - Ticket #1902032: Vulnerability Remediation - Speculative Store Bypass - Updates Required - Ticket #1902035: Vulnerability Remediation - powershellv2 - Update Required - Ticket #1902034: Vulnerability Remediation - Event-Log-Crasher - Update Required - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Dave to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
daveb@bigriversltd.com
daveb@bigriversltd.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Dave, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Open Top Ten report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Dave, Following the quarterly vulnerability review for Big Rivers Ltd, the items below still need remediation. These are typically third-party products or other remaining work that was not included in ticketed first-party remediations. 1. Firebird 2.5.2.26539 (Win32) Affected hosts: Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 What to do: Update Firebird 2.5.2.26539 (Win32) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 2. idrac Affected hosts: idrac - 10.5.5.71 What to do: Update idrac firmware to the minimum version to reach (or the latest available), retire/replace the device if it is not needed, or suppress / accept residual risk when no secure firmware exists (client must be notified or accept; risk remains until a real fix). 3. Adobe Reader XI (11.0.23) Affected hosts: Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 What to do: Update Adobe Reader XI (11.0.23) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). If you would like us to quote this work, or if you will handle it internally, reply to this email. If an item cannot be remediated for business reasons, let me know and I can suppress it from further scan reports. Sincerely, Chris Knospe
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 3
Finding summary:
Windows 10 (all versions) is missing required updates on the listed hosts.
Apply the remaining quality/security updates for the current build via RMM or Windows Update.
Windows 10 is EOL. Do not force a Windows 11 upgrade from this ticket. After the updates, a Windows 11 / new workstation project is a Sales quote and vCIO conversation, then Security suppression of the current OS.
CVE references:
CVE-2025-60724
https://nvd.nist.gov/vuln/detail/CVE-2025-60724
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60724
Additional CVEs (1472 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122878 (or the latest available). Upgrade to a supported Operating System is recommended.
- (1 end-of-life component notices omitted)
Affected Systems:
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [10.0.19045] [1474 vulns]
- ViaworksPC.BRLSERVER - 10.5.5.17 [10.0.19045] [1473 vulns]
- 10.5.5.238 [1473 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- the host is already at/above the minimum version to reach (build/KB)
- the host is already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If the host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After the update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
- Windows 10 is EOL: still apply any remaining quality/security updates first. For a Windows 11 / new workstation project, generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current OS
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Product/System: Microsoft .NET (all versions)
Affected Systems Count: 7
Finding summary:
Microsoft .NET (all versions) is outdated on the listed hosts.
These runtimes update within the same major version. An app built on one major version is tied to that version - removing it will break the app.
CVE references:
CVE-2025-55315
https://nvd.nist.gov/vuln/detail/CVE-2025-55315
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55315
Additional CVEs (72 more) are listed in the Client Folder report.
Affected Systems:
- BR-TS.BRLSERVER - 10.5.5.26 [8.0.11] [150 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [10.0.17763] [50 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [6.0.20] [48 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [6.0.28] [24 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [10.0.11] [15 vulns]
- 10.5.5.238 [5.0.17] [3 vulns]
- 10.5.5.238 [6.0.36] [3 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown, run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client, document what you checked and escalate to Security as a false positive
Quick-check each host first.
Stop and escalate to Security as a false positive if the redistributable/runtime is not present, or is already at or above the minimum version to reach for that major version. Include hostnames and what you found.
Otherwise, choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
Technical guidance:
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET 5: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 10 (LTS): update runtime to the reported target within the 10.x line
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 4
Finding summary:
Microsoft 365 Apps for business - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-70329
https://nvd.nist.gov/vuln/detail/CVE-2026-70329
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70329
Additional CVEs (87 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- BRL-DT-1025A.BRLSERVER (jasonj) - 10.5.5.105 [88 vulns]
- BRL-DT-1025E.BRLSERVER (JamieM) - 10.5.5.115 [88 vulns]
- BRL-DT-1025D.BRLSERVER (shipping) - 10.5.5.139 [88 vulns]
- BRL-DT-1025H.BRLSERVER (daveb) - 10.5.5.154 [88 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or above the minimum version to reach. Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
Technical guidance:
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Product/System: WinVerifyTrust Signature Validation Vulnerability
Affected Systems Count: 12
Finding summary:
WinVerifyTrust Signature Validation Vulnerability is a configuration / hardening finding. Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2013-3900
https://nvd.nist.gov/vuln/detail/CVE-2013-3900
Affected Systems:
- 10.5.5.238 [1 vulns]
- 10.5.5.69 [1 vulns]
- BRL-DT-1025A.BRLSERVER (jasonj) - 10.5.5.105 [1 vulns]
- BRL-DT-1025C.BRLSERVER (JessieW) - 10.5.5.144 [1 vulns]
- BRL-DT-1025D.BRLSERVER (shipping) - 10.5.5.139 [1 vulns]
- BRL-DT-1025E.BRLSERVER (JamieM) - 10.5.5.115 [1 vulns]
- BRL-DT-1025F.BRLSERVER (jessiew) - 10.5.5.83 [1 vulns]
- BRL-DT-1025G.BRLSERVER (tony) - 10.5.5.65 [1 vulns]
- BRL-DT-1025H.BRLSERVER (daveb) - 10.5.5.154 [1 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [1 vulns]
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [1 vulns]
- ViaworksPC.BRLSERVER - 10.5.5.17 [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host/domain first. Stop and escalate to Security as a false positive if the configuration is already correct or the finding does not apply, and include details. Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture: schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- WinVerifyTrust / CVE-2013-3900 is Authenticode hardening - not a software install or Windows Update
- Set EnableCertPaddingCheck=1 under HKLM\Software\Microsoft\Cryptography\Wintrust\Config
- On 64-bit hosts also set the Wow6432Node\...\Wintrust\Config copy
- Prefer domain GPO (or Intune) over one-off registry edits
- Verify signed installers and vendor tools still launch after the change
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Speculative Store Bypass - Updates Required
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required
Product/System: Speculative Store Bypass
Affected Systems Count: 12
Finding summary:
Speculative Store Bypass is a configuration / hardening finding. Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2018-3639
https://nvd.nist.gov/vuln/detail/CVE-2018-3639
Affected Systems:
- 10.5.5.238 [1 vulns]
- 10.5.5.69 [1 vulns]
- BRL-DT-1025A.BRLSERVER (jasonj) - 10.5.5.105 [1 vulns]
- BRL-DT-1025C.BRLSERVER (JessieW) - 10.5.5.144 [1 vulns]
- BRL-DT-1025D.BRLSERVER (shipping) - 10.5.5.139 [1 vulns]
- BRL-DT-1025E.BRLSERVER (JamieM) - 10.5.5.115 [1 vulns]
- BRL-DT-1025F.BRLSERVER (jessiew) - 10.5.5.83 [1 vulns]
- BRL-DT-1025G.BRLSERVER (tony) - 10.5.5.65 [1 vulns]
- BRL-DT-1025H.BRLSERVER (daveb) - 10.5.5.154 [1 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [1 vulns]
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [1 vulns]
- ViaworksPC.BRLSERVER - 10.5.5.17 [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host/domain first. If the configuration is already correct or the finding does not apply, stop and escalate to Security as a false positive, and include details. Otherwise, choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture, schedule it after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Speculative Store Bypass (CVE-2018-3639) is a Windows CPU-mitigation registry setting - not a software install
- Apply latest Windows quality/security updates first - the registry does nothing without those KBs
- Enable the OS mitigation: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
- If FeatureSettingsOverride is missing: set FeatureSettingsOverride=8 and FeatureSettingsOverrideMask=3
- If Override already has a value: add bit 8 (SSB) per Microsoft KB4072698 - do not wipe other Spectre bits already in use
- Prefer domain GPO (or Intune) over one-off registry edits
- Reboot, then verify: Install-Module SpeculationControl; Get-SpeculationControlSettings
- If already patched and mitigations show enabled: escalate to Security as a false positive with hostname, build, and the cmdlet output - then stop
- These mitigations can slow a busy server - discuss with the client if users will notice
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-3639
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Firebird 2.5.2.26539 (Win32) - Update Required - 3rd party application
Vulnerability Remediation - Firebird 2.5.2.26539 (Win32) - Update Required - 3rd party application
Product/System: Firebird 2.5.2.26539 (Win32)
Affected Systems Count: 1
Finding summary:
Firebird 2.5.2.26539 (Win32) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-40342
https://nvd.nist.gov/vuln/detail/CVE-2026-40342
Additional CVEs (5 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.0.10 (or the latest available).
Affected Systems:
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [6 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - powershellv2 - Update Required
Vulnerability Remediation - powershellv2 - Update Required
Product/System: powershellv2
Affected Systems Count: 4
Finding summary:
powershellv2 is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
- Disable Windows PowerShell 2.0 on the system (or the latest available).
Affected Systems:
- 10.5.5.238 [1 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [1 vulns]
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [1 vulns]
- ViaworksPC.BRLSERVER - 10.5.5.17 [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online.
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools.
- Check DHCP (lease, reservation, MAC) for a name.
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP.
- If still unknown: run a network scan from a trusted site host (do not scan from the internet).
- Record the hostname (or device type) on the ticket before remediating.
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive.
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or above the minimum version to reach. Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first. If keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server, that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
Technical guidance:
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify the product from Product + host list. Confirm it is installed on each host before changing anything.
- Update/configure to the version listed under Minimum version to reach when present.
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory. Document the version applied.
- Verify the update was successful.
- If the installer/firmware indicates a reboot or service restart: coordinate with the client first.
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - idrac - Firmware Update Required - 3rd party application
Vulnerability Remediation - idrac - Firmware Update Required - 3rd party application
Product/System: idrac
Affected Systems Count: 1
Finding summary:
idrac firmware/software may be outdated on the listed device(s).
Confirm the real vendor, model, and firmware build on the device first.
Check the vendor security advisory for this CVE and model.
If the vendor documents not affected or already fixed: escalate to Security as a false positive with details and the vendor documentation link.
Otherwise apply manufacturer firmware via the vendor tool or device admin.
Coordinate an outage/reboot window.
CVE references:
CVE-2019-3705
https://nvd.nist.gov/vuln/detail/CVE-2019-3705
Vendor advisory:
https://www.dell.com/support/article/us/en/04/sln316930/dsa-2019-028-dell-emc-idrac-multiple-vulnerabilities?lang=en
Additional CVEs (2 more) are listed in the Client Folder report.
Affected Systems:
- idrac - 10.5.5.71 [3 vulns]
Quick-check each device first.
Then stop (escalate to Security as a false positive) if:
- the device is not present
- already at/above the minimum version to reach
- the finding does not match the installed model/firmware
- the vendor documents this CVE as not applicable or already fixed
Include details and the vendor documentation link.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply firmware / device software (default when keeping the device)
- Apply manufacturer firmware to the version listed under Minimum version to reach (or the latest available for that model).
- If the product line is EOL, still check for and apply the latest available final firmware for that model before anything else.
B. Device not needed - retire / replace / remove from service
- Only if the device should not remain on the network.
C. EOL / no secure path - notify the client, then escalate to Security for suppression
- After confirming the device is on the latest available firmware for that model (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Document model, current firmware, and that latest-available was checked.
- Do not request suppression until latest-available was checked and the client was notified.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree an outage window with the client before applying firmware - the device reboots.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- If a support contract has lapsed, do not apply a software or firmware update.
- Notify the client that updates cannot proceed until support is renewed or a replacement is approved
- Create a Sales quote for support renewal, or for replacement/upgrade if the product is also EOL
- Open a vendor case after entitlement is in place (or to confirm support status)
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
NVD / advisory context:
https://www.dell.com/support/article/us/en/04/sln316930/dsa-2019-028-dell-emc-idrac-multiple-vulnerabilities?lang=en | Dell EMC iDRAC6 versions prior to 2.92, iDRAC7/iDRAC8 versions prior to 2.61.60.60, and iDRAC9 versions prior to 3.20.21.20, 3.21.24.22, 3.21.26.22 and 3.23.23.23 contain a stack-based buffer overflow vulnerability. An unauthenticated remote attacker may potentially exploit this vulnerability to crash the webserver or execute arbitrary code on the system with privileges of the w…
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Event-Log-Crasher - Update Required
Vulnerability Remediation - Event-Log-Crasher - Update Required
Product/System: Event-Log-Crasher
Affected Systems Count: 4
Finding summary:
Event-Log-Crasher is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
- Unofficial security patches (or the latest available).
Affected Systems:
- 10.5.5.238 [1 vulns]
- BR-TS.BRLSERVER - 10.5.5.26 [1 vulns]
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [1 vulns]
- ViaworksPC.BRLSERVER - 10.5.5.17 [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online.
- If you cannot reach it from the usual tools, connect to the site network (VPN, ScreenConnect jump host, or on-site).
- Check DHCP (lease, reservation, MAC) for a name.
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP.
- If still unknown, run a network scan from a trusted site host (do not scan from the internet).
- Record the hostname (or device type) on the ticket before remediating.
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive.
Quick-check each host first:
- Confirm the product is installed on each host before changing anything.
- If the product is not installed, or is already at or above the minimum version to reach, stop and escalate to Security as a false positive. Include hostnames and what you found.
- Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first. If keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
- If this update may interrupt a user, schedule after hours or contact the client first.
- If another vendor manages this application, device, workstation, or server, that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
Technical guidance:
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If the host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify the product from Product + host list.
- Update/configure to the version listed under Minimum version to reach when present.
- If no minimum version is listed: use the CVE/product from this ticket + vendor security advisory, and document the version applied.
- Verify the update was successful.
- If the installer/firmware indicates a reboot or service restart, coordinate with the client first.
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Ticket created by Chris Knospe.Vulnerability Remediation - Adobe Reader XI (11.0.23) - Update Required - 3rd party application
Vulnerability Remediation - Adobe Reader XI (11.0.23) - Update Required - 3rd party application
Product/System: Adobe Reader XI (11.0.23)
Affected Systems Count: 1
Finding summary:
Adobe Reader XI (11.0.23) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
- Update to version 11.0.2 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- Leo-Mini.BRLSERVER (lpinto) - 10.5.5.35 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Confirm Acrobat Pro vs Adobe Reader (and 32 vs 64) on each host before choosing an installer
- Versions 20.x and 21.x are EOL - full upgrade to a supported track, not a security patch on 20/21
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Big Rivers - Alexssa\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Dave,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top Ten):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.