Encryption · Scan · first seen 1 Oct
MediumLikelyOpenMobilefix by 30 Nov
Open · Mobile's
It's Mobile's, but no one has picked it up.
One problem in two places, found by scan, fixed in one, still open in one.
2 sources · 2 places
Scan
First found Thu 1 Oct, last seen Mon 5 Oct
First found Thu 1 Oct, last seen Thu 15 Oct
What closes it
Nobody can mark it fixed by hand. A person submits the fix; a scan or a retest decides it.
27th 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
42 / 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 scanWhat we saw
Accepts TLSv1, TLSv1.1 · Turn off TLS 1.0 and 1.1; offer TLS 1.2 and 1.3 only.
The fix
Turn off TLS 1.0 and 1.1 and weak ciphers at the load balancer; renew certificates before they lapse.
Where
What happened, and what was said
1 event · 0 comments · oldest first