From: Santhapur Naveen <naveens@amiindia.co.in>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Array out of bounds write
Date: Tue, 11 Apr 2017 08:05:58 +0000 [thread overview]
Message-ID: <625A2455CC232F40B0F38F05ACED6D97C867892F@Venus2.in.megatrends.com> (raw)
Hello all,
In the file PxeBcSupport.c of NetworkPkg there is
EFI_STATUS
PxeBcUdp4Write (
{
...
//
// Arrange one fragment buffer for data, and another fragment buffer for header if has.
//
FragCount = (HeaderSize != NULL) ? 2 : 1;
...
TxData->FragmentTable[FragCount - 1].FragmentLength = (UINT32) *BufferSize;
...
}
And similarly in
EFI_STATUS
PxeBcUdp6Write (
{
...
//
// Arrange one fragment buffer for data, and another fragment buffer for header if has.
//
FragCount = (HeaderSize != NULL) ? 2 : 1;
...
TxData->FragmentTable[FragCount - 1].FragmentLength = (UINT32) *BufferSize;
...
}
If HeaderSize is not NULL, then there is a chance of writing array over bounds since FragmentTable is of single element.
///
/// Array of fragment descriptors.
///
EFI_UDP6_FRAGMENT_DATA FragmentTable[1];
Shouldn't we be taking care of this?
Regards,
Naveen
next reply other threads:[~2017-04-11 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 8:05 Santhapur Naveen [this message]
2017-04-11 11:53 ` Array out of bounds write Wu, Jiaxin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=625A2455CC232F40B0F38F05ACED6D97C867892F@Venus2.in.megatrends.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox