Root Cause

Snow.sol has defined a constant PRECISION value to indicate the token decimals. The PRECISION value is currently only used inside the constructor, where it scales the _buyFee argument.

The issue is currently categorized as low in severity, because coincidentally both PRECISION and the decimals() default getter are set to return 18. This issue would've been at a higher severity if both of these values were not equal.

Impact

If both values were not equal, this may had caused decimal mismatches / inconsistencies, mainly for displaying transaction amount.

Proof of Concept (PoC)

Let's assume that right now:

If the contract deployer were to initialize with _buyFee = 5, then:

Mitigation

The fix is to override decimals() by returning PRECISION.