Check deserialization - #109
Merged
Merged
Conversation
Not up to standards ⛔🔴 Issues
|
| Category | Results |
|---|---|
| BestPractice | 2 medium |
🟢 Metrics 4 complexity · 0 duplication
Metric Results Complexity 4 Duplication 0
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
✅ Build pvDataCPP 1.0.89 completed (commit dce8c92291 by @mdavidsaver) |
eg. Array of Structure must have Structure elements.
mdavidsaver
force-pushed
the
check-deser
branch
from
August 10, 2026 00:32
3127bdf to
abc9598
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added validation during deserialization. Check redundancy when encoding array of struct or union. Bound recursion during deserialization.
This change set was developed in response to a confidential security report by Shubham Raj shubham@causalsecurity.com. It is being released early after a subsequent unconfidential report of an overlapping set of issues. Thank you to @anjohnson @dirk-zimoch @simon-ess for review during the embargo period.
cf. epics-base/epics-base#934