-
Notifications
You must be signed in to change notification settings - Fork 254
Bail out of avifDecoderParse() if an essential-required item property is not flagged as essential #537
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
base: main
Are you sure you want to change the base?
Bail out of avifDecoderParse() if an essential-required item property is not flagged as essential #537
Changes from 1 commit
6e37228
9e1d828
2d0a644
69057a7
a26c941
e166009
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -1481,6 +1481,23 @@ static avifBool avifParseItemPropertyAssociation(avifMeta * meta, const uint8_t | |||||||
| } | ||||||||
| } | ||||||||
| if (supportedType) { | ||||||||
| if (!essential) { | ||||||||
| // Verify that it is legal for this property to not be flagged as essential. Any | ||||||||
| // types in this list are *required* in the spec to be flagged as essential when | ||||||||
| // associated with an item. | ||||||||
| static const char * essentialTypes[] = { | ||||||||
| "av1C" // AVIF: Section 2.2.1: "This property shall be marked as essential." | ||||||||
|
||||||||
| "av1C" // AVIF: Section 2.2.1: "This property shall be marked as essential." | |
| "av1C" // AVIF: Section 2.2.1: "This property shall be marked as essential." | |
| "a1op" // AVIF: Section 2.3.2.1: "If associated, it shall be marked as essential." |
Not sure if a1op needs to be handled differently here.
Also, should there be an opposite check for a1lx since the spec says "If associated, it shall not be marked as essential"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. I'm thinking about removing lsel from the list for now and just adding boxes to this list as I add support for new boxes. lsel isn't written or read at all right now, so it seems odd to preemptively block a read on it.
Uh oh!
There was an error while loading. Please reload this page.