Skip to content

Add CVE-2025-25186: DoS vulnerability in net-imap #3489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

nevans
Copy link
Contributor

@nevans nevans commented Feb 8, 2025

CVE-2025-25186 has been reserved and I've asked for it to be published, but it isn't hasn't been reviewed yet. Until then, the advisory is at GHSA-7fc5-f82f-cx69. I recorded the date as 2025-02-11, because I don't know how long the CVE will take.

Cc: @manunio

@nevans nevans requested a review from a team as a code owner February 8, 2025 20:39
@nevans nevans force-pushed the CVE-2025-25186 branch 2 times, most recently from e45c27f to f338a3b Compare February 8, 2025 20:42
title: "CVE-2025-25186: DoS vulnerability in net-imap"
author: "nevans"
translator:
date: 2025-02-11 03:00:00 +0000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think ci is failing because of this line as date is not matching file name, and there are two files one with 2025-02-10 and other with 2025-02-11 was this intentional ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think deleting this file will solve the issue :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, I thought I had pushed that, but I had to run off to do family things with kids so I was in a hurry and missed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants