-
Notifications
You must be signed in to change notification settings - Fork 23
BES1-941: Increase Process name buffer length from 16 to 64 #306
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: support/1.8.5
Are you sure you want to change the base?
Changes from all commits
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 |
|---|---|---|
|
|
@@ -53,7 +53,7 @@ void freeGResult(void *data); | |
| T2ERROR saveGrepConfig(char *name, Vector* grepMarkerList); | ||
| T2ERROR getGrepResults(GrepSeekProfile **GSP, Vector *markerList, bool isClearSeekMap, bool check_rotated, char *customLogPath); | ||
| #define PREFIX_SIZE 5 | ||
| #define BUF_LEN 16 | ||
| #define BUF_LEN 64 | ||
|
||
|
|
||
| typedef struct proc_info | ||
| { | ||
|
|
||
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.
Increasing BUF_LEN increases the size of fixed arrays (e.g., procMemCpuInfo.processName), but current call sites copy into these arrays using length derived from the input string (e.g., memcpy(..., strlen(processName)+1) in dcaproc.c) without bounding to BUF_LEN. This remains a potential buffer overflow if a caller passes a name longer than BUF_LEN-1. Consider switching to a bounded copy (and optionally returning an error or explicitly truncating) everywhere these buffers are written.