Frentzel Products Inc. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-28 | Presenter: Chris Knospe | Export set: Top 7 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Apache Remediation Options: Update to the current version; uninstall if not in use Target Machines: syn-067-052-039-083.biz.spectrum Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: CVE-2021-40438 Remediation Options: Update to the current version; uninstall if not in use Target Machines: syn-067-052-039-083.biz.spectrum Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java 8 Update 281 (64-bit) Remediation Options: Update to version 8.0.5110.32 or later; uninstall if not in use Target Machines: FPI-SPARE01.FrentzelProducts (ksalazar) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: CVE-2018-19052 Remediation Options: Update to the current version; uninstall if not in use Target Machines: syn-067-052-039-084.biz.spectrum Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 0 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 7 vulnerabilities docx report - Ticket #1910041: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1910042: Vulnerability Remediation - Windows Server 2025 - Updates Required - Ticket #1910043: Vulnerability Remediation - Microsoft Defender - 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 George to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
gargiropoulos@frentzelproducts.com
gargiropoulos@frentzelproducts.com
2026 Q4 Vulnerability Scan Follow Up
Good evening George, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 7): Open Top 7 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 George, Following the quarterly vulnerability review for Frentzel Products Inc., 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. Apache Affected hosts: syn-067-052-039-083.biz.spectrum - 67.52.39.83 What to do: Update Apache 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. CVE-2021-40438 Affected hosts: syn-067-052-039-083.biz.spectrum - 67.52.39.83 What to do: 67.52.39.83 Bosch Access Easy Controller (door access), 10.0.0.62 Critical: internet exposed door control panel on a 2009 to 2012 software stack. Source of the Apache CVEs. (multiple CVE's, not just this one, needs a firmware update and/or isolation and possibly remove access... 3. Java 8 Update 281 (64-bit) Affected hosts: FPI-SPARE01.FrentzelProducts (ksalazar) - 10.0.0.135 What to do: Update Java 8 Update 281 (64-bit) 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). 4. CVE-2018-19052 Affected hosts: syn-067-052-039-084.biz.spectrum - 67.52.39.84 What to do: 67.52.39.84 Samsung DVR, 10.0.0.63 High: internet exposed DVR, lighttpd 1.4.26, plain HTTP login. Source of the lighttpd CVEs. (multiple CVE's, not just this one, needs a firmware update and/or isolation and possibly remove access from internet) 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 11 (all versions) - Updates Required
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Product/System: Windows 11 (all versions)
Affected Systems Count: 8
Finding summary:
Windows 11 (all versions) is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (2494 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126653. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5126653. Apply the latest patch. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
- FPI-DT-0724B.FrentzelProducts (twf) - 10.0.0.139 [10.0.22631] [2416 vulns]
- FPI-DT-0724C.FrentzelProducts (ckazimier) - 10.0.0.136 [10.0.22631] [2416 vulns]
- FPI-DT-0724A.FrentzelProducts (bdion) - 10.0.0.140 [10.0.22631] [2416 vulns]
- DESKTOP-52026B.FrentzelProducts (ffuchs) - 10.0.0.148 [10.0.26200] [1616 vulns]
- Desktop-52026A.FrentzelProducts (dpetrowski) - 10.0.0.144 [10.0.26200] [1616 vulns]
- FPI-DT-0126A.FrentzelProducts (hansen) - 10.0.0.128 [10.0.26200] [1616 vulns]
- FPITWFLAPTOP1.FrentzelProducts (twf) - 10.0.0.125 [10.0.26200] [1616 vulns]
- FPI-DT-0724D.FrentzelProducts (gargiropoulos) - 10.0.0.118 [10.0.26200] [1616 vulns]
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:
- already at/above the minimum version to reach (build/KB)
- 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 use 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 this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After 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
===== 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2025 - Updates Required
Vulnerability Remediation - Windows Server 2025 - Updates Required
Product/System: Windows Server 2025
Affected Systems Count: 1
Finding summary:
Windows Server 2025 is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-105016
https://nvd.nist.gov/vuln/detail/CVE-2026-105016
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-105016
Additional CVEs (1620 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126646 (or the latest available).
Affected Systems:
- FPI-HV01 (rradmin) - 10.0.0.15 [10.0.26100] [1621 vulns]
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:
- already at/above the minimum version to reach (build/KB)
- 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 use 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 this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After 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
===== 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Apache - Update Required - 3rd party application
Vulnerability Remediation - Apache - Update Required - 3rd party application
Product/System: Apache
Affected Systems Count: 1
Finding summary:
Apache 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-2017-9788
https://nvd.nist.gov/vuln/detail/CVE-2017-9788
Additional CVEs (46 more) are listed in the Client Folder report.
Minimum version to reach:
- Check Remediation Script (or the latest available).
Affected Systems:
- syn-067-052-039-083.biz.spectrum - 67.52.39.83 [47 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Defender - Update Required
Vulnerability Remediation - Microsoft Defender - Update Required
Product/System: Microsoft Defender
Affected Systems Count: 2
Finding summary:
Microsoft Defender is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-50656
https://nvd.nist.gov/vuln/detail/CVE-2026-50656
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50656
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.1.26080.3 (or the latest available). Update to version 4.18.26060.3008 (or the latest available)
- Update to version 4.18.26060.3008 (or the latest available).
Affected Systems:
- FPILATHE.FrentzelProducts (lathe) - 10.0.0.119 [5 vulns]
- FPI-DT-0724D.FrentzelProducts (gargiropoulos) - 10.0.0.118 [3 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)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- 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) =====
- Check Windows Security on each host: is another EDR/AV active (SentinelOne, Huntress, Webroot, Bitdefender, or similar)?
- If yes and Defender real-time protection is off: that is expected. This finding is a Defender version, not the live AV
- Do not turn Defender real-time protection back on next to that EDR
- If Defender is still the AV, or the platform/service is still running: update platform/signatures via Windows Update or Defender management policy
- Check RMM patch status if patch management is deployed
- Confirm engine/platform version after update
- Then stop if:
- Another EDR is healthy and Defender RTP is off (version/signature age only): notify the client, record discussion notes, escalate to Security for suppression
- Update failed because Defender is fully disabled: same path - the EDR is the control; escalate to Security for suppression
- If the CVE is in a Defender driver or service that is still loaded: update the Defender platform anyway
===== 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - CVE-2021-40438 - Investigate and Resolve - 3rd party application
Vulnerability Remediation - CVE-2021-40438 - Investigate and Resolve - 3rd party application
Product/System: CVE-2021-40438
Affected Systems Count: 1
Finding summary:
CVE-2021-40438 is a CVE-only finding - the scan did not clearly name an installed product.
Identify the real vulnerable component on each listed host before choosing update, uninstall, or suppress.
CVE references:
CVE-2021-40438
https://nvd.nist.gov/vuln/detail/CVE-2021-40438
Vendor advisory:
https://cert-portal.siemens.com/productcert/pdf/ssa-685781.pdf
Affected Systems:
- syn-067-052-039-083.biz.spectrum - 67.52.39.83 [1 vulns]
Quick-check each host first.
Identify the real product or firmware on the host that matches this CVE before remediating.
Then stop (escalate to Security as a false positive) if the CVE does not apply or the component is not present.
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 once the component is identified and still needed)
- After identifying the product/firmware on the host, update to the version listed under Minimum version to reach (or the latest available) or the vendor advisory for that exact product line.
B. Not needed / not in use - uninstall or remove
- Only after you identified the component and confirmed it should not exist on the host.
C. Cannot remediate after identification - escalate to Security for suppression
- You identified the component at a vulnerable version, and update/uninstall is not viable.
- 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:
Once the component is identified: if the change may interrupt a user or service, schedule after hours or contact the client first.
If another vendor manages the identified 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) =====
67.52.39.83 Bosch Access Easy Controller (door access), 10.0.0.62 Critical: internet exposed door control panel on a 2009 to 2012 software stack. Source of the Apache CVEs. (multiple CVE's, not just this one, needs a firmware update and/or isolation and possibly remove access from internet)
===== 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Java 8 Update 281 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Java 8 Update 281 (64-bit) - Update Required - 3rd party application
Product/System: Java 8 Update 281 (64-bit)
Affected Systems Count: 1
Finding summary:
Java 8 Update 281 (64-bit) 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-2022-34169
https://nvd.nist.gov/vuln/detail/CVE-2022-34169
Vendor security center:
https://www.oracle.com/security-alerts/
Additional CVEs (28 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.0.5110.32 (or the latest available).
Affected Systems:
- FPI-SPARE01.FrentzelProducts (ksalazar) - 10.0.0.135 [29 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) =====
- Confirm which Java runtime is installed (vendor + major version, e.g. Oracle 8 / Temurin 11) on each host
- Inventory apps that require that major version before changing anything
- Primary: update within the same major version line to the Minimum version to reach target (or latest security update for that line)
- Oracle Java: Oracle installer / Java Update / enterprise package per client license
- OpenJDK / Temurin-style: Adoptium Temurin or the distro already in use (do not switch vendors without app vendor approval)
- Prefer RMM/automated patching when deployed; else vendor MSI via ScreenConnect
- If unused after dependency check: uninstall that runtime
- Verify java -version / Programs and Features and dependent app startup after change
- Java 8: stay on the existing 8u line unless the app vendor requires a newer major
===== 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - CVE-2018-19052 - Investigate and Resolve - 3rd party application
Vulnerability Remediation - CVE-2018-19052 - Investigate and Resolve - 3rd party application
Product/System: CVE-2018-19052
Affected Systems Count: 1
Finding summary:
CVE-2018-19052 is a CVE-only finding - the scan did not clearly name an installed product.
Identify the real vulnerable component on each listed host before choosing update, uninstall, or suppress.
CVE references:
CVE-2018-19052
https://nvd.nist.gov/vuln/detail/CVE-2018-19052
Vendor advisory:
http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00054.html
Minimum version to reach:
- Check Remediation Script (or the latest available).
Affected Systems:
- syn-067-052-039-084.biz.spectrum - 67.52.39.84 [1 vulns]
Quick-check each host first.
Identify the real product or firmware on the host that matches this CVE before remediating.
Then stop (escalate to Security as a false positive) if the CVE does not apply or the component is not present.
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 once the component is identified and still needed)
- After identifying the product/firmware on the host, update to the version listed under Minimum version to reach (or the latest available) or the vendor advisory for that exact product line.
B. Not needed / not in use - uninstall or remove
- Only after you identified the component and confirmed it should not exist on the host.
C. Cannot remediate after identification - escalate to Security for suppression
- You identified the component at a vulnerable version, and update/uninstall is not viable.
- 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:
Once the component is identified: if the change may interrupt a user or service, schedule after hours or contact the client first.
If another vendor manages the identified 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) =====
67.52.39.84 Samsung DVR, 10.0.0.63 High: internet exposed DVR, lighttpd 1.4.26, plain HTTP login. Source of the lighttpd CVEs. (multiple CVE's, not just this one, needs a firmware update and/or isolation and possibly remove access from internet)
===== 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): ...\Frentzel Products Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening George,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 7):
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.