I'm seeing this in SystemEngine 1.1.2 puddle 2013-01-31.1

Example URL: http://qeblade40.rhq.lab.eng.bos.redhat.com/pulp/ks/redhat/Dev/content/dist/rhel/server/6/6Server/x86_64/os/updateinfo.xml

IRC snippet:
<jmatthews> aweiteka, the updateinfo.xml file is likely to be corrupted for clients who look at it
<jmatthews> it could break some yum plugins looking at security updates, bugfixes, etc


Might this be why Available Errata never displays?

Fixed upstream: http://yum.baseurl.org/gitweb?p=yum.git;a=commit;h=6e56ea6a6236dde080d60f091a7854d204825bd4

Confirmed CDN repo[1] is valid XML. The issue appears to be introduced in katello.

<jmatthews> aweiteka, I think the issue comes down to does systemEngine determine errata by looking at updateinfo.xml or by querying Pulp through API

The other impact would be to yum plugins such as yum-plugin-security

[1] http://download.lab.bos.redhat.com/devel/jgregusk/share/d267c7a02d6beac9559ee2d17570371346f9c2c4acae57ab4438f4bddd60cfcc-updateinfo.xml

Katello gets errata updates from a pulp api query. I used pulp-admin to confirm pulp is returning errata.

Reducing severity to medium. If admins use yum plugins to query katello updates would not be returned properly.

SRT is classifying this as security hardening and not a security flaw since there is no explicit way for an attacker to trigger this.

Pulp hasn't used yum to parse or render errata in a long time, so this was likely fixed long ago.

This should no longer be an issue, closing it as UPSTREAM. If you are still seeing this issue, please feel free to re-open.