Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Bug Report: Invisible Unicode warning for footnote in README

For my README.md, BitBucket reports "This file contains invisible Unicode characters that have been substituted and highlighted. Executing code that contains these invisible characters can have unexpected and malicious results." The only highlighted area is at the end of the file shows '<U00a0>' which is a no-break space, and comes at the end of a footnote just before a link back to the footnote in the text - `<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text">↩</a>`.

 

My guess is that the Markdown parser that BitBucket uses to render footnotes is putting that Unicode equivalent of `&nbsp;` before the backlink, and AFTER that happens, BitBucket runs the 'check for potentially malicious invisible Unicode characters' plugin.

This doesn't harm anything, but it is demonstrably a false-positive warning.

 

I recommend either moving the Unicode check to before the Markdown render, or whitelisting the offending Unicode character U00a0 in the Unicode checker, or change the setting of the Markdown renderer to avoid emitting characters that will trigger the malicious Unicode checker.

2 answers

Same thing is happening now in our README.md files. You've just recently released an update that broke our formatting in README files. How do we disable this functionality?

 

 

2023-03-14 13_52_17 [1333x137].png

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 13, 2023

Hi @osep_redmine,

Welcome to the community and thank you for reaching out!

I have reached out to the development team regarding this issue, I will let you know as soon as I have an update.

Kind regards,
Theodora

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 20, 2023

Hi @osep_redmine and @marius_guscius ,

Our development team has deployed on production a fix for this issue.

Could you please let me know if the issue is resolved for you?

Kind regards,
Theodora

Looks fixed, thank you!

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 21, 2023

Thank you for the update and you are very welcome!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events