To answer your question “How is this possible?” I have to explain how the plugin detects these changes. The plugin uses the checksum [1] of the files provided by the official WordPress releases and compares them with the checksum of the files in your website, if they are different the plugin flags the files are “modified”.
However, instead of downloading a fresh copy of WordPress every time you execute the integrity check, it uses a public API available here [2] that allows people to retrieve the checksum of all the files for a specific version. It seems that the API is returning outdated data because the checksum of the “license.txt” and “controls.svg” files appear to differ from the checksum detected in your installation. The plugin has no control over this information, it barely uses the data that WordPress provides.
If you want to remove the warning, go to the plugin’ settings page, click on “Scanner” then scroll down until “WordPress Integrity Diff Utility”, enable this tool then go to the dashboard again and click the filenames, the plugin will show a popup with the differences present in that file. If you consider these differences to be harmless you can select the file and mark it as fixed using the form below the table. Otherwise, select the files and execute the “Restore” action from the same form.
[1] https://api.www.ads-software.com/core/checksums/1.0/?version=4.8
[2] https://en.wikipedia.org/wiki/Checksum