A quick search of the docs page reveals that it was fixed in 4.3.2.
http://docs.splunk.com/Documentation/Splunk/4.3.2/ReleaseNotes/4.3.2
If you ever want to know about known issues or fixes per version always have a look at the release notes first.