TLDR Index
Daily Editions
Contents
  1. Page 1: Today’s IndexTLDR, TLDR AI, TLDR Web Dev, TLDR InfoSec, TLDR Crypto · 9 stories
  2. Page 2: TLDRTLDR · 7 stories
  3. Page 3: TLDR AITLDR AI · 12 stories
  4. Page 4: TLDR Web DevTLDR Web Dev · 10 stories
  5. Page 5: TLDR InfoSecTLDR InfoSec · 10 stories
  6. Page 6: TLDR CryptoTLDR Crypto · 11 stories
  7. Page 7: TLDR DesignTLDR Design · 11 stories
  8. Page 8: TLDR FoundersTLDR Founders · 12 stories
  9. Page 9: TLDR MarketingTLDR Marketing · 11 stories
  10. Page 10: Resources & ToolsTLDR, TLDR AI, TLDR Web Dev, TLDR InfoSec, TLDR Design, TLDR Founders, TLDR Marketing · 16 stories
  11. Page 11: SponsoredTLDR, TLDR AI, TLDR Web Dev, TLDR InfoSec, TLDR Founders · 6 stories
?
Keyboard shortcuts
← / →
Previous / next page
↑ / ↓
Scroll while full screen
PgUp / PgDn
Scroll by viewport
Space
Scroll down by viewport
Shift+Space
Scroll up by viewport
Home
First page
End
Last page
F
Full screen
Escape
Exit immersive mode

Daily Edition · Page 5

THE DAILY INDEX

Technology, AI, software, security, crypto and business

ATTACKS & VULNERABILITIES

TLDR InfoSec

TLDR InfoSec

EYECARE & HEALTHTECH COMPANY EXPOSED ALMOST 5 MILLION RECORDS

Jeremiah Fowler discovered an unencrypted, non-password protected database containing 4.8 million records belonging to AI optometry software company Care1. The database contained eye exams in PDF format which included patient PII, doctor's comments, and images of the exam results. The database also included spreadsheets that contained patient addresses, personal health numbers, and other PHI. Care1 removed the database after it was notified of the exposure.

vpnmentor.com · 4 min

TLDR InfoSec

THE CURIOUS CASE OF AN EGG-CELLENT RESUME

An in-depth look at a sophisticated campaign conducted by TA4557/FIN6 that utilized a resume lure to compromise a system. The fake resume zip contained a malicious .lnk file which was used to start an execution flow with several LOLBins payloads to establish a foothold. The threat actor then established persistence by deploying C2 software and creating a new user before performing recon to discover a target for lateral movement. The threat actor then compromised and pivoted to a Veeam backup server which they used to compromise another server. The attacker then utilized Cloudflared and Cobalt Strike for persistence but didn't perform any more actions before being evicted.

thedfirreport.com · 20 min

TLDR InfoSec

THE QUALCOMM DSP DRIVER - UNEXPECTEDLY EXCAVATING AN EXPLOIT

This technical analysis examines several vulnerabilities discovered in Qualcomm's adsprpc driver, which Google's Threat Analysis Group found was being exploited in the wild. The researchers identified six different bugs, including CVE-2024-43047, which involved a use-after-free vulnerability that could be triggered through map collisions in the driver's memory management system. By analyzing kernel panic logs from the exploit, the researchers determined that attackers were likely using inotify_event_info objects to exploit the vulnerability, highlighting how chipset drivers remain one of the weakest links in Android's security model in 2024.

googleprojectzero.blogspot.com · 32 min

TLDR InfoSec

PERFORMING ANDROID STATIC ANALYSIS 101-A COMPLETE GUIDE FOR BEGINNERS

This is a comprehensive guide to Android Static Analysis, which is a method of examining Android applications for security vulnerabilities without executing them. It covers several essential tools including APKTool, MobSF, Dex2jar, JD-GUI, Androguard, Ghidra, and APKleaks, explaining how each tool can be installed and used to analyze different aspects of Android applications such as permissions, hardcoded credentials, and potential security risks. The tools work together to create a robust security analysis approach, with each tool offering unique capabilities - from decompiling APKs to inspecting code and identifying vulnerabilities in the early stages of development.

laburity.com · 8 min

TLDR InfoSec

MICROSOFT RECALL SCREENSHOTS CREDIT CARD NUMBERS AND SOCIAL SECURITY NUMBERS

The author of this post was investigating the efficacy of Microsoft Recall's “sensitive information” filter, which comes enabled by default in the current Windows Insider build, and found that it still captured credit card information and SSNs. The researcher tested entering credit card numbers into a Notepad file with clear text delineating it as a credit card number, filled out a PDF of a loan application in Microsoft Edge that included an SSN and other personal information, and even created an HTML page that had a text input explicitly requesting credit card information and found that Recall copied all of them. Recall did omit capturing information inputted in actual shopping sites though.

tomshardware.com · 3 min

TLDR IndexPage 5