5.0.0-rc2-dev Custom Field searchable without permission #43383
Replies: 14 comments
-
I can confirm this, but also that we can do very little about this. The content from the custom field is indexed as part of the content item and all content from the content item has the same viewlevel assigned to it. The best that we can do here is to add a warning text to the field that the content is handled with the same viewlevel as the content item it belongs to. |
Beta Was this translation helpful? Give feedback.
-
Can't the access level be checked at indexing? |
Beta Was this translation helpful? Give feedback.
-
What do you want to check? The currently logged in user when indexing definitely has the permissions and when searching we only have the access level of the original content item. Considering that the content of the custom fields is not displayed when searching, this is not a high risk to me. |
Beta Was this translation helpful? Give feedback.
-
Just an idea, can't there be a acl columnn in jos_finder_terms ? |
Beta Was this translation helpful? Give feedback.
-
Adding that column would pretty likely be the death to any performance the system has right now. As I said previously, I also consider this actually a rather minor issue and would solve it with a warning at most. Again, this would affect you if you deliberately added the custom field to the index, knew a specific value to search for and the only thing you would get out of this is a list of content items containing this. It still would not display the content of the custom field. |
Beta Was this translation helpful? Give feedback.
-
I think you are downplaying the potential severity of this information disclosure. If I have indexed a directory of members with a boolean field "is_a_spy" them I only need to knbow the field exists to enumerate the data |
Beta Was this translation helpful? Give feedback.
-
I already installed RC2 to use it in a new project for a catalog. Normal users are only able to search by a unique QR Code like 639ww6934g923zgb##ddhsddd - Registered Users are able to search by serial number of the product but not registered are not allowed to. Thats my "security issue" right now to solve. |
Beta Was this translation helpful? Give feedback.
-
No, that actually is not correct. We are not indexing the name of the field, but just the value of the field. So for your scenario to be correct, you would have to have used "is_a_spy" for the field. I'd say it is much more likely, that you would have used a boolean value here. Regardless of that, you would have to explicitely have enabled the field to be indexed. We are not indexing this stuff by default. |
Beta Was this translation helpful? Give feedback.
-
That is why your previous suggestion is important otherwise people will be "suprised" just as @coolcat-creations has been
|
Beta Was this translation helpful? Give feedback.
-
See #42111 |
Beta Was this translation helpful? Give feedback.
-
I think 42111 is ok as a quick fix, but would like to remain the issue opened to maybe find a solution to solve it in future |
Beta Was this translation helpful? Give feedback.
-
When field indexed as taxonomy (option And when the field indexed as "metadata" (options |
Beta Was this translation helpful? Give feedback.
-
@Fedik that is correct. |
Beta Was this translation helpful? Give feedback.
-
Seems to me sovled for now. Converting it to discussions for more ideas |
Beta Was this translation helpful? Give feedback.
-
Steps to reproduce the issue
Create a custom field and set access level to Super User
Set the custom field to be added to search index
Create an article and fill the field with an unique value
Search by that unique value
Expected result
If you are logged in you should be able to find the content
If not you should not be able to find it
Actual result
Can be found also if logged out
Beta Was this translation helpful? Give feedback.
All reactions