Repository navigation
Security Watch 1.1.1
Fixes for feeds that were read wrongly and for two checks that trusted a name. No configuration change. To be published under the default latest tag; the GitHub Action is used as uses: ShieldaAI/security-watch@v1.1.1.
Fixed
- Feeds with an image in
<media:content>were read without their text. The article in<description>was ignored whenever an item also had a<media:content>element, so every item from feeds such as Rapid7's blog and Dark Reading arrived with an empty description and could match only by its title. The first ofcontent:encoded,content,descriptionandsummarythat holds text is now used. An emptycontent:encodedalso falls through to the description. - Feeds that escape their HTML with entities showed the tags as text. A description written as
<p>(Tenable's blog, the seclists.org lists) arrived as the literal text<p>,<br>and similar, which reached matching, models and alerts. A field that carries HTML (RSSdescriptionandcontent:encoded, Atomcontentandsummarywithtype="html") and holds no raw<, which escaped XML text never does, is now unescaped once as XML (the five predefined entities and character references only; DTDs are still refused) before it is read as HTML. CDATA and plain-text fields (titles, Atom text content) are read as before, so<script>in a title stays text. The first scan after the upgrade records a new revision of items from such feeds that are still in the news window. - A name that starts like a loopback address no longer counts as one.
intake.listen: 127.example.com:8787was accepted without TLS orallow_plain_http, because the check read the text of the host. Onlylocalhost, an IPv4 address in 127.0.0.0/8 and the IPv6 loopback address count now. sbom --project FILErefuses a symbolic link. A link named like a dependency file was followed to whatever it pointed at, unlike files found inside a project folder, which were already skipped. A project folder given as a link is still read.