Skip to content

[FP]: Microsoft.Extensions.Hosting.Systemd nuget is not systemd #8841

Open

Description

@mormegil-cz

Package URl

pkg:nuget/Microsoft.Extensions.Hosting.Systemd@10.0.12

CPE

cpe:2.3:a:systemd_project:systemd:10.0.12:*:*:*:*:*:*:*

CVE

No response

ODC Integration

{"label" => "CLI"}

ODC Version

13.0.0

Description

Dependency Checker reports usage of the (.NET) Nuget package “Microsoft.Extensions.Hosting.Systemd” against the systemd vulnerabilities (e.g. CVE-2018-15688, CVE-2017-18078, etc. etc.).

Activity

  1. github-actions commented on Oct 14, 2026

    @github-actions
    Contributor

    Nuget Coordinates

    dotnet add package Microsoft.Extensions.Hosting.Systemd --version 10.0.12

    Suppression rule:

    <suppress base="true">
        <notes><![CDATA[
        FP per issue #8841
        ]]></notes>
        <packageUrl regex="true">^pkg:nuget/Microsoft\.Extensions\.Hosting\.Systemd@.*$</packageUrl>
        <cpe regex="true">cpe:/a:systemd_project:systemd(:.*)?$</cpe>
    </suppress>

    Link to test results: https://github.com/dependency-check/DependencyCheck/actions/runs/38555702976

  2. chadlwilson commented on Oct 14, 2026

    @chadlwilson
    Collaborator

    Can you please share an xml or json or html report from ODC? Our FP automation is not seeing this false positive with a CLI scan.

  3. mormegil-cz commented on Oct 14, 2026

    @mormegil-cz
    Author

    Report for a trivial reproducible project: owasp-report.json

  4. chadlwilson commented on Oct 14, 2026

    @chadlwilson
    Collaborator

    Thanks, will take a look. For some reason the automation is running against ODC 12.2.2 instead of 13.0.0 which might be the reason for the discrepancy as some tidy-ups were done in 13.0.0 to reduce false negatives which did unfortunately re-introduce some false positives.

  5. chadlwilson commented on Oct 14, 2026

    @chadlwilson
    Collaborator

    It does look like this report is showing them against pkg:generic/Microsoft.Extensions.Hosting.Systemd@10.0.13 not against a nuget package.

    That's important as the suppression rule must match the ecosystem. Where did you get the nuget PURL from? A report? Or you "guessed" it?

  6. mormegil-cz commented on Oct 14, 2026

    @mormegil-cz
    Author

    Oh, that one is funny: I did not want to upload the report for my real project (which reported the PURLs as in the original bugreport, I copy&pasted them from the report), so I created a small repro project. However, I created the project using the new .slnx solution format. In that case, ODC creates the PURLs as pkg:generic. So I recreated the repro project using the old .sln format, and ODC uses pkg:nuget again: owasp-report.json

    So, apparently, ODC does not support .slnx (or, rather, it behaves a bit strangely in that case).

    And… I tried 12.2.2 which seems to generate exactly the same report. AFAICT, the only difference between my case and the Github Action is that I’m running ODC on the current .NET 10 instead of .NET 8 (which is supported only until November, IIANM) used by the action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions