scan.nextcloud.com reports wrong data
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Nextcloud security scanner scan.nextcloud.com doesn't reflect real config.
Scanner relies on public information according to description
Our scan is strictly based on publicly available information
But there are few checks related to information not publicly exposed e.g. have-I-been-pawned, MFA and brute-force protection. In my test instance I disabled some security measures and re-trigger the scan. Surprisingly the scan still reports brute-force protection and MFA enabled - while this are effectively inactive in the instance as shown in the screenshot (e.g. all MFA providers are disabled)
It seems the scanner has some assumptions build-in and doesn't reflect effective system config. If an admin would rely on the scanner chances exist insecure system settings exist while the scanner is "all green".
Please improve the detection or remove broken checks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reproducing the scan with MFA providers, brute-force protection, and Have I Been Pwned checks disabled, then compare the reported results with the effective configuration. Done means the scanner accurately detects these settings or the broken checks are removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100