Skip to content
Tools / FreeRADIUS / Security

Security Deep Dive

FreeRADIUS

Security posture and CVE patch evidence from tracked releases.

Back to Tool

4 critical dependency CVEs affects release_3_0_28.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Dormant cadence · 142d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
SLSA provenance Unknown
Attestation predicate level Latest release
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 17d ago
Release cadence: dormant Present
142d median over recent releases Release history
Latest release: 1d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 3d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 1d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 1d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 1d ago
3.7/10 Security Score
4.8/10 Scorecard
Dependency Exposure 16 transitive dependency CVEs found in the latest SBOM. 4 critical.

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

1d stale

scorecard

1.92 / 4.0

Score 4.8/10

cve health

0.00 / 2.5

⚠ No direct scan — 4c/5h transitive CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 26.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

7.4

10%

supply chain risk: 26.0 transitive cves: 4c/5h

Provenance trust

provenance trust

4.8

40%

scorecard score: 4.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none
How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 26.0/100
4 Transitive critical CVEs
0 KEV-transitive CVEs
100% Dependency freshness

Scorecard

Scorecard 4.8/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check Score Reason
Maintained 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Security-Policy 10 security policy file detected
Code-Review 0 Found 0/30 approved changesets -- score normalized to 0
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow 0 dangerous workflow patterns detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
License 10 license file detected
SAST 0 no SAST tool detected
Binary-Artifacts 10 no binaries found in the repo
Fuzzing 10 project is fuzzed
Signed-Releases 8 5 out of the last 5 releases have a total of 5 signed artifacts.
Branch-Protection 3 branch protection is not maximal on development and all release branches
Packaging 10 packaging workflow detected
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

25 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

4

High

5

Medium

6

Low

0

Unknown

1

Critical 4 High 5 Medium 6 Unknown 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2017-18342 critical pyyaml release_3_2_9
CVE-2019-20477 critical pyyaml release_3_2_9
CVE-2020-14343 critical pyyaml release_3_2_9
CVE-2020-1747 critical pyyaml release_3_2_9
CVE-2013-0294 high pyrad release_3_2_9
CVE-2023-1428 high grpcio release_3_2_9
CVE-2023-32731 high grpcio release_3_2_9
CVE-2023-33953 high grpcio release_3_2_9
CVE-2023-4785 high grpcio release_3_2_9
CVE-2013-0342 medium pyrad release_3_2_9
CVE-2021-46823 medium python-ldap release_3_2_9
CVE-2023-32732 medium grpcio release_3_2_9
CVE-2025-61911 medium python-ldap release_3_2_9
CVE-2025-61912 medium python-ldap release_3_2_9
GHSA-r8wq-qrxc-hmcm medium python-ldap release_3_2_9
CVE-2017-8359 unknown grpcio release_3_2_9

Showing 16 of 16

Beta — feedback welcome: [email protected]