Mason Buettner
7fa7e8f26d
Update link for vulnerability processing documentation ( #48031 )
...
Updating a broken link and move link.
2026-06-23 09:47:38 -04:00
Dante Catalfamo and Noah Talerman
48fe442da0
Update CVE documentation to list Linux distributions supported ( #46828 )
...
**Related issue:** Resolves #45110
---------
Co-authored-by: Noah Talerman <noahtal@umich.edu >
2026-06-05 16:22:39 -04:00
Noah Talerman
2432c20412
Vulnerabilities: Clarified information on macOS built-in Python ( #45226 )
...
- Also move false positives call out box higher up
2026-05-15 09:03:58 -04:00
Noah Talerman
158d968136
Vulnerability coverage ( #42497 )
...
Currently, Fleet doesn't support CVEs for Debian or Fedora packages. OS
(kernel CVEs) are supported
For the following bug:
- https://github.com/fleetdm/fleet/issues/40230
2026-03-27 14:37:41 -04:00
+1
cc671f98c9
Preview of v4.82.0 doc changes ( #38894 )
...
This PR will remain in draft as a preview of upcoming documentation
changes for 4.82.0
---------
Co-authored-by: Jordan Montgomery <elijah.jordan.montgomery@gmail.com >
Co-authored-by: Marko Lisica <83164494+marko-lisica@users.noreply.github.com >
Co-authored-by: Magnus Jensen <magnus@fleetdm.com >
Co-authored-by: Victor Lyuboslavsky <2685025+getvictor@users.noreply.github.com >
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com >
Co-authored-by: Dante Catalfamo <43040593+dantecatalfamo@users.noreply.github.com >
Co-authored-by: melpike <79950145+melpike@users.noreply.github.com >
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com >
Co-authored-by: Nico <32375741+nulmete@users.noreply.github.com >
Co-authored-by: Scott Gress <scottmgress@gmail.com >
2026-03-12 18:19:53 -05:00
Konstantin Sykulev and Mike Thomas
43c312131d
Updating docs to inform there is no os aware cve scanning ( #39452 )
...
**Related issue:** Resolves #35190
---------
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com >
2026-02-06 16:01:10 -06:00
Ian Littman
f34c366e95
Clarify how we match Fedora vulns, repoint "coming soon" for RHEL kernel vulns from superseded issue to current issue ( #39102 )
2026-02-02 09:48:00 -05:00
Mason Buettner
aa0581176f
Clarify reporting of specific software configuration vulnerabilities ( #36299 )
...
Added note about reporting vulnerabilities that impact specific software
configurations.
2025-11-27 11:57:43 -05:00
Graham Williams
0b3f9bbe96
Update link for vulnerability processing documentation ( #35262 )
...
Updates broken link for vulnerability-processing.md
2025-11-13 08:38:08 +00:00
Rachael Shaw
86b80e28ed
Documentation v4.76.0 ( #34943 )
...
Documentation changes for the 4.76 release
2025-11-11 09:30:14 -05:00
jacobshandling
c9a14d5038
Update vuln processing guide, add change file for JetBrains IDE extension vulns ( #34478 )
...
Addresses #32266
Update docs, add change file
2025-10-17 17:39:21 -05:00
+1
48cb0908cd
Docs v4.74.0 ( #33879 )
...
Documentation changes for 4.74
---------
Co-authored-by: Marko Lisica <83164494+marko-lisica@users.noreply.github.com >
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com >
Co-authored-by: Victor Lyuboslavsky <2685025+getvictor@users.noreply.github.com >
Co-authored-by: Ian Littman <iansltx@gmail.com >
Co-authored-by: Noah Talerman <noahtal@umich.edu >
Co-authored-by: Lucas Manuel Rodriguez <lucas@fleetdm.com >
Co-authored-by: Magnus Jensen <magnus@fleetdm.com >
Co-authored-by: Jordan Montgomery <elijah.jordan.montgomery@gmail.com >
Co-authored-by: Janis Watts <184028114+jmwatts@users.noreply.github.com >
Co-authored-by: Allen Houchins <32207388+allenhouchins@users.noreply.github.com >
2025-10-06 17:03:10 -05:00
Marko Lisica
7bd96c7453
Update vulnerability coverage table ( #32149 )
...
Related to:
- #30738
2025-10-02 13:26:06 +02:00
+2
2a901105bf
Docs v4.73.0 ( #32682 )
...
Documentation changes for the 4.73.0 release
---------
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com >
Co-authored-by: Marko Lisica <83164494+marko-lisica@users.noreply.github.com >
Co-authored-by: Ian Littman <iansltx@gmail.com >
Co-authored-by: Victor Lyuboslavsky <2685025+getvictor@users.noreply.github.com >
Co-authored-by: Gabriel Hernandez <ghernandez345@gmail.com >
Co-authored-by: Magnus Jensen <magnus@fleetdm.com >
Co-authored-by: RachelElysia <rachel@fleetdm.com >
Co-authored-by: RachelElysia <71795832+RachelElysia@users.noreply.github.com >
Co-authored-by: Lucas Manuel Rodriguez <lucas@fleetdm.com >
Co-authored-by: Scott Gress <scottmgress@gmail.com >
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com >
2025-09-08 19:09:44 -05:00
Jahziel Villasana-Espinoza and Noah Talerman
e50d913bc0
add note about support for fedora and centos coming ( #32095 )
...
# Checklist for submitter
Closes #32027
---------
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com >
2025-08-19 16:49:26 -04:00
Jahziel Villasana-Espinoza
3c49123205
update article with linux kernel vulns info ( #32022 )
...
> Closes #31215
2025-08-19 09:28:20 +09:00
Ian Littman
7a54a2de22
Include non-primary CVSS scores from NVD when a primary score doesn'texist for a given CVSS version ( #29199 )
...
Fixes #28261 .
~~Of note, this logic will prefer a non-primary CVSSv3.1 score over a
primary CVSSv3.0 score if 3.1 doesn't have primary but 3.0 does. I
haven't seen any evidence of this in our dataset (looked at 2024
output).~~
Updated with logic that will prefer a primary CVSSv3.0 score over a
secondary CVSSv3.1 score for a given vulnerability. In the test dataset
(2023 vuln snapshot, ~20k vulns) there were no cases where this
situation presented itself, so output was identical to the prior
implementation.
Validated by comparing a vulns run from GitHub Actions to a local run
with the new code, and confirmed that existing v3 scores weren't
replaced when they already existed (just got adds of v2 when only v3
existed, and v2/v3 adds when no scoring existed).
Confirmed that all three CVEs mentioned in #28261 show up in feed data.
Added spot-checks for secondary CVSS scores to the feed validator tool.
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
<!-- Note that API documentation changes are now addressed by the
product design team. -->
- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files )
for more information.
- [x] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [x] Manual QA for all new/changed functionality
2025-05-29 13:03:19 -05:00
Luke Heath
7380919dc3
Organize contributor docs and establish ADR process and template ( #29101 )
2025-05-17 15:03:52 -05:00
Ian Littman
31715f8639
Fix typo in vuln processing article ( #27996 )
...
I'm sure this was my typo. Sorry about that!
2025-04-08 16:29:37 -04:00
Ian Littman
44f9a0882f
Correct vuln processing false positive cleanup timeout ( #26399 )
...
The timeout is hardcoded to 2x vulns job periodicity (default one hour).
See
http://github.com/fleetdm/fleet/blob/main/docs/Contributing/Vulnerability-processing.md#false-positive-cleanup
for contributor docs on this.
2025-02-17 17:14:17 -06:00
Noah Talerman
4805fb2244
It takes some time for false positives to disappear ( #26329 )
...
Documentation for the following bug:
- #25898
2025-02-14 16:20:46 -05:00
Ian Littman
86eddbbdb7
Add note on vulnerability software name matching to vulnerability processing docs ( #25881 )
...
Adding given current state and 2025-01-28 discussion on software
uniqueness and how it interacts with vulnerability processing.
2025-01-30 09:07:19 -05:00
Tim Lee
c4ec018e75
Docs - update vuln sources ( #23388 )
...
adding detail to docs vulnerability sources
reference:
https://github.com/fleetdm/fleet/issues/22564#issuecomment-2445071589
2024-10-30 11:30:58 -05:00
Ian Littman
5500f3362e
Update vulnerability processing docs to reference goval-dictionary ( #21536 )
...
Docs PR for #20934 , split from #21506
2024-08-26 21:38:03 -05:00
2171544ad1
Docs quick reference optimization ( #21331 )
...
This PR closes https://github.com/fleetdm/fleet/issues/21108
@noahtalerman, I double-checked all redirects, and they are working.
Clicking through the URLs in [this
spreadsheet](https://docs.google.com/spreadsheets/d/1djVynIMuJK4pT5ziJW12CluVqcaoxxnCLaBO3VXfAt4/edit?usp=sharing )
is a pretty quick way to go through them all. Note that "Audit logs" and
"Understanding host vitals" redirect to the contributor docs on GitHub,
so they will throw a 404 until this is merged.
Some new guides benefitted from a name change, so they make more sense
as stand-alone guides, and also so that we don't have to mess around
with more redirects later. Those name changes followed [this
convention](https://fleetdm.com/handbook/company/communications#headings-and-titles ),
which was recently documented in the handbook.
Have fun!
---------
Co-authored-by: Eric <eashaw@sailsjs.com >
Co-authored-by: Noah Talerman <noahtal@umich.edu >
2024-08-16 15:30:31 -05:00