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 · 8 stories
  3. Page 3: TLDR AITLDR AI · 11 stories
  4. Page 4: TLDR Web DevTLDR Web Dev · 11 stories
  5. Page 5: TLDR InfoSecTLDR InfoSec · 11 stories
  6. Page 6: TLDR CryptoTLDR Crypto · 11 stories
  7. Page 7: TLDR ProductTLDR Product · 10 stories
  8. Page 8: TLDR DesignTLDR Design · 11 stories
  9. Page 9: TLDR FoundersTLDR Founders · 13 stories
  10. Page 10: TLDR MarketingTLDR Marketing · 12 stories
  11. Page 11: Resources & ToolsTLDR, TLDR AI, TLDR Web Dev, TLDR InfoSec, TLDR Design, TLDR Founders · 14 stories
  12. Page 12: SponsoredTLDR, TLDR AI, TLDR Web Dev, TLDR InfoSec, TLDR Product, TLDR Founders · 9 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

RESEARCHERS CRACK MICROSOFT AZURE MFA IN AN HOUR

Researchers from Oasis Security discovered an MFA bypass on one of Microsoft Azure's MFA methods that could lead to the compromise of Microsoft 365 accounts. The researchers discovered that the endpoint did not implement rate limiting and that the auth period lasted for a full three minutes as opposed to the recommended 30 seconds. The researchers also discovered that an attacker could rapidly make many auth attempts to enumerate the full 6-digit MFA space.

darkreading.com · 4 min

TLDR InfoSec

SECURING AWS LAMBDA: HOW MISCONFIGURATIONS CAN LEAD TO LATERAL MOVEMENT

AWS Lambda functions are popular attack vectors for credentials theft and lateral movement. This post presents a realistic application architecture and walks through a scenario in which an attacker exploits a vulnerability in a Lambda function to achieve code execution and pivots to data exfiltration. It suggests using hardened IAM roles, secure coding practices, and monitoring to mitigate Lambda attacks.

sentinelone.com · 10 min

TLDR InfoSec

RETROFITTING SPATIAL SECURITY TO HUNDREDS OF MILLIONS OF LINES OF C++

Google has made a large push to move to memory safe languages but in the process is embracing hardening C++ to bridge the gap. The security team has attempted to harden libc++ by adding bounds checking to improve spatial security. The team started by integrating the changes into the test and preproduction environment for a year before promoting to production for all but a few exceptions. The safety checks only add a 0.3% performance overhead, but they have resulted in the discovery of over 1,000 bugs and successfully interfered with a red team engagement.

security.googleblog.com · 7 min

TLDR InfoSec

EVERYDAY GHIDRA: GHIDRA DATA TYPES — CREATING CUSTOM GDTS FROM WINDOWS HEADERS — PART 2

This second part of a guide on "Everyday Ghidra" explains how to create custom Ghidra Data Type (GDT) files from Windows headers to improve reverse engineering. You can ensure accurate and efficient analysis of binaries by using a compiler to preprocess headers before submission to Ghidra. Training Ghidra to use NDIS data types enhances the decompilation process and reveals new structures and variables for better analysis.

links.tldrnewsletter.com · 11 min

TLDR InfoSec

OVER 600 VULNERABILITIES FOUND IN AVERAGE SOFTWARE CONTAINER

NetRise compiled advanced SBOMs for 70 of the most downloaded containers on DockerHub and found that the average container had over 600 vulnerabilities. 45% of the vulnerabilities were 2-10 years old and 7.9% were over 5 years old. 4.2% of high and critical vulnerabilities were being actively exploited. NetRise also noted that many components did not include manifests and emphasized the importance of advanced SBOMs.

techmonitor.ai · 4 min

TLDR InfoSec

HACKING TERRAFORM STATE FOR PRIVILEGE ESCALATION

This article discusses hacking Terraform state for privilege escalation by modifying the state file to control infrastructure changes without a "terraform apply." Attackers can manipulate the state file to delete resources or take over a deployment pipeline, which is why it is important to secure and lock the Terraform state to prevent unauthorized changes. The article highlights the need to use a read-only role for "terraform plan" executions to inspect changes without altering infrastructure until the deployment step.

plerion.com · 12 min

TLDR IndexPage 5