View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
19611 | Bug reports | Security | public | 2024-06-13 13:02 | 2024-06-18 10:20 |
Reporter | Mazi | Assigned To | tibor.pacalat | ||
Priority | none | Severity | partial_block | ||
Status | closed | Resolution | won't fix | ||
Product Version | 6.5.x | ||||
Summary | 19611: Security: Remove sensitive information like passwords from phpinfo | ||||
Description | This is the first time I have seen this, but there may be some systems for which phpinfo exposes very sensitive data like the DB password, see attached screenshot. A default admin user with permissions to access phpinfo could get access to data they should not see. Question is: Can we somehow remove such details from the default phpinfo? | ||||
Steps To Reproduce | Steps to reproduceThis may be difficult to reproduce since the customer uses a special Kubernetes setup which is pretty custom. I have never seen such details at a phpinfo before. Expected result(Write here what you expected to happen) Actual result(Write here what happened instead) | ||||
Tags | No tags attached. | ||||
Bug heat | 256 | ||||
Complete LimeSurvey version number (& build) | 6.5.3 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | MySQL | ||||
Server OS (if known) | |||||
Webserver software & version (if known) | |||||
PHP Version | 8.2 | ||||
@DenisChenu, have you ever seen an exposure like this before? |
|
Hmm, from looking at the code I don't think anyone except superadmin can see this info |
|
I don't see it on your screenhost : too little. The fix are not so old about restriction, maybe forcedsuperadmin only ? |
|
@DenisChenu I don't understand what you wrote, sorry. |
|
You mean about ForcedSuperAdmin ? I mean : by defult : user #1 have access to all since he have access to FTP and DB parameters. Simple super admin didn't have access to all. Then maybe restriction to forced super admin reference |
|
:+1: |
|
Looks like only superadmins can access this. And it surely is a thing of setting ENV variables (wrong) and then these can get exposed. |
|
Clearly not,
|
|
As I see it, this is not an issue on the application side -> closing this issue. |
|
@tibor.pacalat: Can you remove the screenshot I attached and make this public? |
|
Done |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2024-06-13 13:02 | Mazi | New Issue | |
2024-06-13 13:02 | Mazi | File Added: image.png | |
2024-06-13 13:02 | Mazi | Assigned To | => tibor.pacalat |
2024-06-13 13:02 | Mazi | Status | new => assigned |
2024-06-13 13:03 | Mazi | Note Added: 80323 | |
2024-06-13 13:03 | Mazi | Bug heat | 256 => 258 |
2024-06-13 16:57 | tibor.pacalat | Note Added: 80331 | |
2024-06-13 16:57 | tibor.pacalat | File Added: Screenshot 2024-06-13 at 16.56.33.png | |
2024-06-13 16:57 | tibor.pacalat | Bug heat | 258 => 260 |
2024-06-13 17:19 | DenisChenu | Note Added: 80335 | |
2024-06-13 17:19 | DenisChenu | Bug heat | 260 => 262 |
2024-06-13 17:39 | tibor.pacalat | Note Added: 80338 | |
2024-06-13 18:15 | DenisChenu | Note Added: 80343 | |
2024-06-13 18:16 | DenisChenu | Note Added: 80344 | |
2024-06-13 19:40 | Mazi | Note Added: 80349 | |
2024-06-13 20:28 | DenisChenu | Note Added: 80350 | |
2024-06-14 10:11 | tibor.pacalat | Note Added: 80362 | |
2024-06-14 10:11 | tibor.pacalat | Status | assigned => closed |
2024-06-14 10:11 | tibor.pacalat | Resolution | open => won't fix |
2024-06-18 10:10 | Mazi | Note Added: 80384 | |
2024-06-18 10:20 | DenisChenu | File Deleted: image.png | |
2024-06-18 10:20 | DenisChenu | View Status | private => public |
2024-06-18 10:20 | DenisChenu | Bug heat | 262 => 256 |
2024-06-18 10:20 | DenisChenu | Note Added: 80385 |