Skip to content
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

[GHSA-8hvv-gchf-jqcp] tif_dirread.c in LibTIFF 4.0.7 has an "outside the range... #5327

Conversation

Crispy-fried-chicken
Copy link

Updates

  • Affected products
  • Summary

Comments
According to the description of the GHSA, the affected version of the vulnerability is 4.0.7. However, based on the vulnerability code snippet, this vulnerability still exists in earlier versions, such as 4.0.0. Please confirm.
code sippet:
{
uint8* ma;
float* mb;
uint32 n;
ma=(uint8*)origdata;
mb=data;
for (n=0; n<count; n++)
*mb++=(float)(*ma++);
}

@github-actions github-actions bot changed the base branch from main to Crispy-fried-chicken/advisory-improvement-5327 March 2, 2025 18:55
@shelbyc
Copy link
Contributor

shelbyc commented Mar 3, 2025

👋 Hi @Crispy-fried-chicken, I can't make changes to any of the advisories for which you've submitted community contributions because none of the affected products are in one of the GitHub Advisory Database's supported ecosystems. Products written in C are almost never part of a supported ecosystem.

However, the accuracy of CVE records is important. If you find an aspect of a CVE record you believe is inaccurate, I recommend that you contact the CVE Numbering Authority (CNA) listed in each record. You can find contact information for each CNA at https://www.cve.org/PartnerInformation/ListofPartners.

For example, the CNA for CVE-2017-7597 is MITRE, and MITRE's CNA profile links to their MITRE CVE Request web form where members of the public can request changes to CVE records.

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