-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Security issue allows to view all graphs #2964
Comments
@george-kar, we need a CVE on this, can you log one? |
Wow good find @george-kar !!!! |
@cigamit I cant open CVE as the activation email never arrived. Can you please let me know if you already fix it and there is a fix on it? UPDATE: Requested CVE on https://cveform.mitre.org |
I see the fix but you have wrong post mention (2954). Please fix your code fix with the 2964 instead of 2954. |
Initial commit was here: 7a6a172 |
If you see commit mentions 2954 instead of 2964. People cannot track commit with the proper thread. |
Without rebasing, the commit history cannot be changed. It will not be changed. So, if necessary, pull the two commit references to highlight the mistake during commit. |
CVE-2019-16723 was assigned for this issue. |
This should be the last permission issue around data export issues.
Quoting Debian bug report #941036:
@cigamit any comment? Can you confirm that this vulnerability was introduced in cf73ae1? |
Yea, that's a good point. I know why I made the original change. Let me see if I can redo the fix. |
* CVE-2019-16723 Security issue allows to view all graphs * Thischange restores the check inside of lib/rrr.php and updates all but on calling of the graph function to include the user.
Okay, this has been fixed correctly now. |
Comments for cfb0733
More comments for other
|
|
With regards to the older parameters, it may be worth cycling between the release (git checkout release/) and seeing when it became unused. I haven't had time to do that yet, but that's usually what I do to vet why a parameter is suddenly appearing extraneous. |
As my previous comments, we can take action below:
Before go thru rrdtool_function_graph usage from each cacti and plugins delivered release(0.x to 1.x) |
Is there any issue you think in keeping it null though for some of the calls? |
@hlef, $xport_meta used in graph_xport.php for CSV export. |
@ddb4github, since xport_meta is pass by reference, I'm not sure which the best approach would be. It would be really nice if browsers 'could' hide the address bar. However, I know why they are doing it... Phishing attack. |
Missing security user pass in graph_realtime.php for "Security issue allows to view all graphs"
Just one comment about So I think we can safely remove BTW, the newest
PR for a temp fix before we remove |
…and graph impage page
BTW, plugin_npc/top_graph_header.php:147: print trim(rrdtool_function_graph($_GET["local_graph_id"], $_GET["rra_id"], $graph_data_array)); |
NPC is still kind of waiting for someone to take it over. It's in kind of an archive status. |
I have created a user with no group membership. Graph permission default is DENY and I have selected all graphs Restricted instead of 1. I have device params default DENY and only set to specific one. Template perm is set to DENY. Tree Perms is also default DENY and I set to access only a specific one. When I login with that user I see only one option in tree and when I click on the device I see the graph. Everything is fine. But if I take the url
domain.com/graph_json.php?rra_id=0&local_graph_id=3205&graph_start=1569069730&graph_end=1569156130&graph_height=120&graph_width=500
and change the local_graph_id with another value ie 5312 I get a response and inside that response I see the image which is base64. If I decode and create png I can see the other graph that I dont have permission to see.
I tried to update to latest cacti 1.2.6 and it still get that security issue. I also checked the source code carefully and I don't see any permission check regarding graphs. For example I see permission check for tree node creation but not for graphs.
The text was updated successfully, but these errors were encountered: