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.
[Warning] This PR is generated by AI
Pull Request Description
PR Title: Fix for Vulnerability in PcapPlusPlus - OSV-2024-382
PR Description:
UdpLayer
class, where functions were accessing data beyond the bounds of the allocated buffer. This occurred when the buffer size was insufficient for operations involving UDP header fields, leading to a heap-buffer-overflow. The issue was reported in the OSV-2024-382 vulnerability report.getSrcPort()
: Ensures that the buffer length is sufficient before accessing the source port.getDstPort()
: Ensures that the buffer length is sufficient before accessing the destination port.computeCalculateFields()
: Ensures that the buffer length is sufficient before performing length and checksum calculations.These changes ensure that unsafe memory access is avoided, improving both the security and stability of the program.
Sanitizer Report Summary:
UdpLayer
class while accessing UDP header fields. The root cause was the lack of bounds checking before accessing these fields, leading to out-of-bounds memory access.Full Sanitizer Report:
Files Modified:
Packet++/src/UdpLayer.cpp
Patch Validation: The patch has been validated and confirmed to resolve the issue identified in the sanitizer report. No new bugs were introduced.
Links: