-
Notifications
You must be signed in to change notification settings - Fork 0
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
Heap Out-Of-Bounds Memory Access at ParseSegmentIsoAtoms /inchi/INCHI_API/inchi_dll/ichiread.c:5003:14 #1
Comments
@jan-keller Is this active? Seems like a very old bug in a package without clear maintainers. |
Hello @ebradbury, this bounty is still active. It has just been posted. Good hunting! |
Yes, part of the challenge will be to get the fixed merged. |
Hi, has anyone figured out who to contact to have the fixes merged? |
Any progress? |
I've contacted the authors and they'll publish an updated repo to github
sometime this month.
At that point we can see if the patch i prepared is still applicable and
close the ticket.
Il Lun 2 Gen 2023, 15:01 Kunam Balaram Reddy ***@***.***> ha
scritto:
… Any progress?
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWGJD4D2W3CJDO44Y43FRXTWQLNR5ANCNFSM6AAAAAARV73V7Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@TheScavenger13 did you really just copy my entire ticket and point to my fork? |
Funny! |
You need to create a fork and start maintaining it. The original repo is obviously abandoned. |
Last i've heard the owner of the project indicated mid june but i think its
going to be a while yet for the official github repo to be published.
Il Gio 8 Giu 2023, 08:30 abebeos ***@***.***> ha scritto:
… Yes, part of the challenge will be to get the fixed merged.
You need to create a fork and start maintaining it. The original repo is
obviously abandoned.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWGJD4GK2JWW2G6P2KHXNALXKFWRFANCNFSM6AAAAAARV73V7Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I even fail to locate the sources on SF... |
Details at issuetracker.google.com/74097108
The text was updated successfully, but these errors were encountered: