Version 3.4.0.0 is the latest Stable release.
It can be downloaded from here:
https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.exe
https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.msi
Version 3.4.0.0 is the latest Stable release.
It can be downloaded from here:
https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.exe
https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.msi
Based on customer requests we've examined ways to update Portable Apps, like apps form the SysInternals bundle.
There are many ways to achieve this, but we wanted one that works well with the Custom Software feature in VulnDetect.
We also wanted to avoid making one Config per App in the SysInternals bundle.
And, since these files can live in various places, including folders that are writable by non-privileged users, we wanted to be careful not to overwrite the wrong files or follow symbolic links.
The script will not overwrite files unless they have the company name specified in the $companyNameToCheck
variable, it will also not touch files in the $excludedDirs
.
The combination of Custom Software and this script assumes that you add a ZIP archive as an Additonal File and that the ZIP archive contains a folder called "files" with all the SysInternal files you want to replace, e.g. the entire SysInternals bundle.
You can also edit the $sourceDir
variable if you want to use a different layout in your ZIP archive.
The below script was created by ChatGPT (by OpenAI). It was created based on the above requirements and it has been reviewed and tested by SecTeer.
Note: This script is intended to run in an automated fashion and with a sub folder of known trusted files. Executing this in the wrong location and altering variables and conditions may have unforeseen consequences, because the script overwrites files recursively.
# Define the company name to check for
$companyNameToCheck = "Sysinternals - www.sysinternals.com"
# Get the current working directory and set the source directory to the "files" subfolder
$sourceDir = Join-Path -Path (Get-Location) -ChildPath "files"
$drive = "C:\"
# List of directories to exclude (common shim file locations)
$excludedDirs = @(
"$env:SystemRoot\AppPatch",
"$env:SystemRoot\System32\ShimCache"
)
# Function to get the latest file from a directory
function Get-LatestFile {
param (
[string]$directory,
[string]$fileName
)
$files = Get-ChildItem -Path $directory -Filter $fileName
$latestFile = $files | Sort-Object LastWriteTime -Descending | Select-Object -First 1
return $latestFile
}
# Function to check the "Company Name" and "Product Name" properties of a file
function Get-FileProperties {
param (
[string]$filePath
)
$properties = Get-ItemProperty -Path $filePath -Name 'VersionInfo'
return @{
CompanyName = $properties.VersionInfo.CompanyName
ProductName = $properties.VersionInfo.ProductName
}
}
# Function to recursively replace files in the target directory with the latest from the source directory
function Replace-Files {
param (
[string]$sourceDir,
[string]$drive,
[string]$companyNameToCheck
)
# Get the list of files in the source directory
$sourceFiles = Get-ChildItem -Path $sourceDir
# Iterate over each file in the source directory
foreach ($sourceFile in $sourceFiles) {
# Get the latest version of the source file
$latestSourceFile = Get-LatestFile -directory $sourceDir -fileName $sourceFile.Name
# Find matching files in the drive recursively, excluding the source directory and excluded directories
$matchingFiles = Get-ChildItem -Path $drive -Filter $sourceFile.Name -Recurse -ErrorAction SilentlyContinue | Where-Object {
$_.FullName -notlike "$sourceDir*" -and
$excludedDirs -notcontains $_.DirectoryName
}
# Replace each matching file with the latest source file if the company name matches and it is not a Chocolatey shim file
foreach ($targetFile in $matchingFiles) {
$properties = Get-FileProperties -filePath $targetFile.FullName
if ($properties.CompanyName -eq $companyNameToCheck -and $properties.ProductName -notlike "*Chocolatey Shim*") {
Copy-Item -Path $latestSourceFile.FullName -Destination $targetFile.FullName -Force
Write-Output "Replaced $($targetFile.FullName) with $($latestSourceFile.FullName)"
} else {
Write-Output "Skipped $($targetFile.FullName) as it is either not from '$companyNameToCheck' or it is a Chocolatey shim file"
}
}
}
}
# Call the function to replace files
Replace-Files -sourceDir $sourceDir -drive $drive -companyNameToCheck $companyNameToCheck
@OLLI_S There are a few users, yes.
The website doesn't really state anything at all:
https://pcmanager.microsoft.com/en-us
I'll leave it as Untracked and Pre-release for now, do let me know if you see some official statement that I can link to and then we'll flag the EXE edition as EoL.
@OLLI_S From what I can see, then detection of Rufus and SumatraPDf is working as expected. As you know, part of our detection relies on the original filenames, so when an app or user renames EXE files, it easily (and intentionally) bypasses our detection.
Is FileZilla a standard sub application of Cygwin?
Perhaps we should bundle it?
@OLLI_S We actually stopped bundling it a long time ago. When I look at your results, then I see all the 365 Apps.
There are two reasons we stopped bundling it. One is that Microsoft frequently releases unknown builds to a subset of systems, this breaks some logic that we rely upon. The other is that the Suite system doesn't support packages, so in order to support updating 365 Apps, we had to stop using the Suite bundle.
We may change this eventually, but it's not on the roadmap at the moment.
Btw. if some of your 365 Apps disappear, then it may be because you ran into one of those Unknown builds, please ping me directly, next time you only see some of them, then I can verify whether this is the reason.
@OLLI_S Yes, I can see they changed some properties. It should be fixed now.
Thank you for reporting this.
Thank you for letting us know (btw. we base it on the legal owner of the website, not the company name in the EXE, but the legal entity on the website has changed too).
We've tweaked the detection, do let us know if it has improved.
We've updated the links for Edge and Edge WebView2, thank you.
Edge WebView2 is a tad special, as there is different editions, some which are intended to be bundled with third party apps and then there is one which is system wide and can be shared by apps that need it.
The system wide one can be updated by simply running the latest installer, which is what we do, when you let VulnDetect update it.
The alternative is to let the built-in (Edge) updater update it.
Since many different applications use WebView2, it often takes time before it is updated (i.e. it often requires a system restart because important files are in use).
@OLLI_S Good questions.
Most customers who requested this feature, want to periodically review the apps that they Ignored.
They are not deleted, they can simply be extended.
Yes, users do get an email stating that some Ignore rules will expire within X days.
On the Configuration page, there is a tab with Ignore rules, simply highlight X number of rules and click the Renew button, and they should be extended with another 90 days.
No, they all expire after 90 days by default.
Again, feedback is welcome on this feature, after you have used for a while. We are not certain that it is ideal, so we are open for suggestions once it has been used in "real life" for a while,
@OLLI_S Thank you for the suggestion, it will be reviewed.
@OLLI_S Thank you for the suggestion, we will consider it, next time we review UI features.
Hi Greg,
Indeed, on the 10th November 8.108.0.205 was the default version available for download, since it appears it has been reverted.
Thank you for letting us know, we will let 8.107.0.215 remain recommended for a bit longer.
A quick follow up on this.
Yesterday, we conducted "The Purge", it involved deleting thousands of accounts, sadly we based this on IP addresses extrapolated from obvious SPAM/SCAM accounts. This clearly proved that a few specific countries known for underpaid labour and SPAM factories are central to this.
Thus, we have decided to implement IP based filtering. As crude and prejudiced as it may be, it is simply the easiest way to combat the majority of this frustrating and wasteful flooding.
If you have been impacted by this and have a legitimate interest in the site, please contact us by other means and we will help you restore access to the forum.
Hi,
Welcome to VulnDetect dot org, the forum for discussing SecTeer VulnDetect and related subjects.
Sadly, we have been flooded with SPAM and SCAM posts from simpleminded individuals, criminals and underpaid off-shore workers.
We have therefore started a crude campaign to delete a vast number of accounts and the posts they attempt to make.
Sadly, it appears that we occasionally delete a legitimate post or user. We apologize for that.
Doing a proper vetting of a single registration and post is simply too time consuming.
We have therefore changed the registration process, so first of all you have to answer a simple question, it appears to stop half of the simpleminded individuals who are tasked with spamming sites such as ours, the rest, that means both legitimate users and scammers with a bit of cognitive abilities has to wait for an admin to reject or accept their profile.
We will attempt to do this daily, but can't promise that it always will be done in a timely fashion.
Most users who should have access to this site either already have a connection to a user in our community or knows an employee who works here. If not, please do spend a few minutes on the forum or on the parent website, to find alternate contact information and send us a request to approve your profile and post.
We apologize for all this, but we want to ensure that this forum has a high degree of relevant posts, without boring scam posts about ED, travel advice, erotic services and similar totally irrelevant and probably fraudulent content.
Thank you for your patience and understanding!
@WacoJohn My apologies for this.
Please see this response:
https://vulndetect.org/post/6673
@WacoJohn With regards to the "rejection", then I am deeply sorry if that happened. We have received an excessive amount of SCAM posts recently, so our purge might have been a tad excessive.
We did change the way we approve profiles instead, as we have thousands of "ghost" profiles.
To anyone else who gets rejected or "not-approved", please do not hesitate to contact us by other means, and we'll try to find you in the pile of fake profiles and SCAM posts and approve it.
@WacoJohn Welcome to VulnDetect.
The Personal edition of VulnDetect only supports one Agent (installation / PC) per account (email).
I think this may be the reason for the confusion.
If you want to control 3 PC's, then I can give you a "Corporate" account, however, it is intended for a larger number of PC's than 3, so it may also not fit super well.
Our goal is to merge the Personal UI and the Corporate UI, so we get a more user friendly edition of the Corporate. However, I don't have any ETA on that project.