Hey! I'm trying to understand how the paginator behaves and why it does what it does. Here's some info about the paginator: Paginator Info:

Page Number: 2

Total Pages: 3

Has Next: true

Has Prev: true

Pages on Current Page:

Title: CASE: ATLASSIAN CONFLUENCE - Date: 2023-12-18 21:00:49.275 +0000 UTC

Title: Proudest work - Date: 2023-11-25 18:19:40.938 +0000 UTC

Title: Online test article - Date: 2023-10-21 21:24:59.335 +0000 UTC

Title: Test article with image - Date: 2023-10-05 21:18:58.567 +0000 UTC

Title: Test case - Date: 2023-10-02 13:03:04.852 +0000 UTC

Title: Test artikel - Date: 2023-10-02 12:58:44.246 +0000 UTC

Title: CASE: APACHE LOG4J2 - Date: 0001-01-01 00:00:00 +0000 UTC

Title: CASE: SMBv3 SERVER COMPRESSION TRANSFORM HEADER MEMORY CORRUPTION - Date: 0001-01-01 00:00:00 +0000 UTC

Title: Chris travels for Coordinated Vulnerability Disclosure to Japan - Date: 0001-01-01 00:00:00 +0000 UTC

Title: ๐’๐š๐ฏ๐ž ๐ญ๐ก๐ž ๐ƒ๐š๐ญ๐ž: ๐„๐ฑ๐œ๐ฅ๐ฎ๐ฌ๐ข๐ฏ๐ž ๐„๐ฏ๐ž๐ง๐ญ ๐Ÿ๐จ๐ซ ๐๐š๐ซ๐ญ๐ง๐ž๐ซ๐ฌ - Date: 0001-01-01 00:00:00 +0000 UTC

Title: Securing the Digital World: No, We Donโ€™t Steal Credentials - Date: 0001-01-01 00:00:00 +0000 UTC

Title: xx - Date: 0001-01-01 00:00:00 +0000 UTC

CASE: ATLASSIAN CONFLUENCE

Nadat Veloxity een zero-day kwetsbaarheid had geรฏdentificeerd, werkten DIVD, DTC en NSM samen om 18.469 kwetsbare ISP's op de hoogte te stellen.

case

Proudest work

intro proudest work

Online test article

This is the online intro

Test article with image

This is the introduction text of the article

Test case

This is a test case

Test artikel

Introductie case

xx

xx

Securing the Digital World: No, We Donโ€™t Steal Credentials

On our website, you might have found a page called โ€˜how we deal with leaked credentialsโ€™ or spotted the case โ€˜DIVD-2020-00013 Leaked phishing credentialsโ€™. Does this mean that our volunteers send out phishing emails and leak the obtained credentials of innocent victims? Of course not!

๐’๐š๐ฏ๐ž ๐ญ๐ก๐ž ๐ƒ๐š๐ญ๐ž: ๐„๐ฑ๐œ๐ฅ๐ฎ๐ฌ๐ข๐ฏ๐ž ๐„๐ฏ๐ž๐ง๐ญ ๐Ÿ๐จ๐ซ ๐๐š๐ซ๐ญ๐ง๐ž๐ซ๐ฌ

Weโ€™re excited to welcome our partners to a special evening marking our 5th anniversary.

Chris travels for Coordinated Vulnerability Disclosure to Japan

With the support of the Dutch embassy in Tokyo, I have researched Coordinated Vulnerability Disclosure (CVD) in Japan. I had the opportunity to travel to Japan from October 22 to November 22. During my stay, I interviewed security researchers from various governmental institutes, companies, and universities and spoke with hackers, most of whom were foreign nationals residing in Japan. I also participated in conferences and meetings: KEIO Cybersecurity Conference (30-10/1-11), Cyber Risk Meetup (1-11), TengueSec meetup (13-11), CodeBlue (14-11/15-11), and AVTokyo (16-11). One of the highlights of my trip was organizing a CVD expert meeting with the Dutch embassy on the 13th of November. The last days I spent in the beautiful coastal village of Kamakura to start writing this report.

CASE: SMBv3 SERVER COMPRESSION TRANSFORM HEADER MEMORY CORRUPTION

On March 10, 2020, Microsoft published information about a serious vulnerability in Microsoftโ€™s Server Block Protocol version 3. The vulnerability (CVE-2020-0796) is a remote code execution vulnerability that exists in the way that the Microsoft Server Message Block 3.1.1 (SMBv3) protocol handles certain requests.

CASE: APACHE LOG4J2

Apache reported a remote code execution vulnerability in Apache Log4j2, the vulnerability in the Log framework of Apache makes it possible to misuse the record log information feature. This makes it possible for an attacker to construct special data request packets through this vulnerable component, and ultimately trigger remote code execution.