I can just confirm that the same thing exists in the newest firmware, therefore it's probably not a bug but rather a flaw in it's specifications.