Bug 111
Summary: | There maybe some risks to printf the addr of the map page | ||
---|---|---|---|
Product: | DPDK | Reporter: | andy01011501 |
Component: | ethdev | Assignee: | Gaetan Rivet (grive) |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | ajit.khaparde, stephen |
Priority: | Normal | ||
Version: | 17.11 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
andy01011501
2018-11-27 13:35:24 CET
Gaetan, Can you please take a look? Thanks Ajit Hi, Andy could you please be more specific? What risk do you see? As I see it, the DPDK application is run with the right to map addresses exposed by *IO drivers. A user having the right to see the DPDK app logs would have the same rights to discover those mappings directly from *IO. Hi Gaetan, I don't think it is a good idea to expose the address in the log,but it is just a risk,we can ignore it. The issue is that logged messages go to syslog, and there maybe malware that has access to syslog and can use the that message to find addresses for other damage. |