Exposure · Scan · first seen 8 Oct
HighLikelyOpenMobilefix by 7 Nov
Last seen by a scan that could see it · Standard scan of tessellate.ng, Thu 8 Oct
Standard scan of tessellate.ng, Thu 15 Oct couldn't test for it properly, so it stays open. Only a complete scan of the same depth can close it.
One problem in one place, found by scan.
1 source · 1 place
Scan
First found Thu 8 Oct
What closes it
Nobody can mark it fixed by hand. A person submits the fix; a scan or a retest decides it.
10th of 39 in your queue
Proof first, then exploitation in the wild, a public exploit, EPSS and severity, adjusted for exposure and how much the asset matters
Priority
60 / 100
What each source saw
As each source gives it · secrets, keys and card numbers stay masked
The scan's case file · tessellate.ng
See it in that scanWhy it matters here
Error pages show environment values and file paths to anyone who causes an error.
What we saw
Errors show a full stack trace with environment values, file paths and the framework version.
https://agents.tessellate.ngWhoops! There was an error. APP_ENV: production
The fix
Set APP_DEBUG=false in production and clear the config cache.
Where
What happened, and what was said
1 event · 0 comments · oldest first