Skip to content

Add advisory for tor-circmgr TROVE-2024-003 #1957

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 3 commits into from
May 19, 2024

Conversation

ijackson
Copy link
Contributor

There are going to be two advisories. There are in fact two bugs due to entirely different code paths, with similar impact.

I am making these as separate MRs since doing otherwise would probably break some tooling.

Comment on lines 2 to 27
[advisory]
id = "RUSTSEC-0000-0000"

package = "tor-circmgr"

date = "2024-05-15"

url = "https://github.com/mystuff/mycrate/issues/123"

references = ["https://gitlab.torproject.org/tpo/core/arti/-/issues/1409"]

# There doesn't seem to be an applicable category for
# "privacy weaking due to protocol misimplementation".
# There ought to be "information-leak".
categories = []

keywords = ["tor", "privacy", "information-leak"]

# We have applied for a CVE
aliases = ["TROVE-2024-003"]

related = ["TROVE-2024-004"]

# This is the default for parsers, apparently, but legally,
# we ought to have an explicit licence grant, which this can serve as:
license = "CC0-1.0"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the review. I prefer to keep the newlines, unless they're against RUSTSEC policy, as I find it makes things more readable.

I seem to have failed to set the URL field indeed. I will fix that.

@Shnatsel
Copy link
Member

Thank you for the report, and sorry for the delay!

I've added the CVE ID now that a CVE has been assigned. I'll merge as soon as CI passes.

@Shnatsel Shnatsel merged commit 0a336b8 into rustsec:main May 19, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants