I would say a lot depends on if the users are remote, or are on the local machine. I would disable the feature if you do not need it.
Local user / attacker:
If the users are local, an attacker can find out most (but not all) of this information fairly easily, although this report would certainly make it easier for the attacker. Even locally, there are a couple pieces of data that would probably be hard to obtain by other methods that could be useful to attackers.
- I see component buffer size as being troublesome because it could aid in buffer overflow attacks.
- Depending on the implementation of the database, database name or possibly component could aid in a SQL injection attack as well (if PeopleSoft is vulnerable to this, which I do not know). Most of the other information can aid in an attack, but is generally available at the local machine anyway.
Remote user / attacker:
If the users are remote, this report is far more problematic. It reveals many details that would be useful to attackers, which would be harder for them to obtain through other means. For example, the OS, browser, service pack, etc... would let the attacker know what they are attacking and if it is out of date (so they know what vulnerabilities there are).
I would highly recommend disabling this feature if you do not need it and there are remote users.