[MAGNOLIA-3161] Some UTF-8 characters do not pass through security checks Created: 22/Mar/10  Updated: 23/Mar/10  Resolved: 23/Mar/10

Status: Closed
Project: Magnolia
Component/s: admininterface, core, security
Affects Version/s: 4.3
Fix Version/s: 4.3.1

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-3150 SimpleUrlPattern do not accept all th... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Since 4.3 it is possible to have UTF-8 characters in the names of the nodes. However some of such characters do not pass security checks and once inserted will result in access to the node/page being denied to a user. Example is small latin th character with strikethrough (U-1D7A).
To reproduce:

  • log in as superuser and create page in AdminCentral
  • enter the character in the name of the page
    The error message saying user doesn't have access to the node will appear as a result. Making dump of the nodes in Tools/JCR queries will show the page with the utf character in the name properly, however the page is no longer visible in the website view in AdminCentral.


 Comments   
Comment by Fabrizio Giustina [ 23/Mar/10 ]

Hi Jan, this looks like MAGNOLIA-3150, that should be fixed with 4.3.1. Can you check using the new release?

Generated at Mon Feb 12 03:43:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.