Thanks for the response.
I am using mcr.microsoft.com/mssql/server:2025-CU2-ubuntu-24.04 as the container image.
G
geraldizo_0690
@geraldizo_0690
0
Reputation
24
Posts
1
Profile views
0
Followers
1
Following
Best posts made by geraldizo_0690
This user hasn't posted anything yet.
Latest posts made by geraldizo_0690
-
RE: Increased Incorrect Classification of Security Vulnerabilitiesposted in Support
-
RE: Increased Incorrect Classification of Security Vulnerabilitiesposted in Support
These are our configuration for automatic assessment.
-
RE: Increased Incorrect Classification of Security Vulnerabilitiesposted in Support
Perhaps this list can help you on investigation!
---- Begin: ---- cryptography 39.0.2 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853) <p>cryptography 39.0.2 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 39.0.2 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853) <p>cryptography 39.0.2 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 40.0.2 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853) <p>cryptography 40.0.2 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 40.0.2 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853) <p>cryptography 40.0.2 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 40.0.2 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853) <p>cryptography 40.0.2 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 40.0.2 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853) <p>cryptography 40.0.2 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 43.0.1 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853) <p>cryptography 43.0.1 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 43.0.1 is Noncompliant in daasi-group. Reason: Vulnerability (PGV-2610853) <p>cryptography 43.0.1 is Noncompliant in daasi-group.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 43.0.1 is Noncompliant in daasi-group. Reason: Vulnerability (PGV-2610853) <p>cryptography 43.0.1 is Noncompliant in daasi-group.</p> <p>Reason: Vulnerability (PGV-2610853)</p> ---- Begin: ---- cryptography 45.0.7 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 45.0.7 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 45.0.7 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 45.0.7 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 45.0.7 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 45.0.7 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.2 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.2 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.2 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.2 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.2 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.2 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.2 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.2 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.3 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.3 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.4 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.4 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.4 is Noncompliant in pypi. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.4 is Noncompliant in pypi.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- cryptography 46.0.4 is Noncompliant in pypi-combined. Reason: Vulnerability (PGV-2610853); No license detected <p>cryptography 46.0.4 is Noncompliant in pypi-combined.</p> <p>Reason: Vulnerability (PGV-2610853); No license detected</p> ---- Begin: ---- inetutils-telnet 2:2.4-2+deb12u1 is Noncompliant in debian. Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected <p>inetutils-telnet 2:2.4-2+deb12u1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected</p> ---- Begin: ---- inetutils-telnet 2:2.4-2+deb12u2 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected <p>inetutils-telnet 2:2.4-2+deb12u2 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected</p> ---- Begin: ---- inetutils-telnet 2:2.4-2+deb12u3 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected <p>inetutils-telnet 2:2.4-2+deb12u3 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected</p> ---- Begin: ---- klibc-utils 2.0.12-1 is Noncompliant in debian. Reason: Vulnerability (PGV-2603766); Vulnerability (PGV-2603774); Vulnerability (PGV-2603772); No license detected <p>klibc-utils 2.0.12-1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603766); Vulnerability (PGV-2603774); Vulnerability (PGV-2603772); No license detected</p> ---- Begin: ---- klibc-utils 2.0.14-1 is Noncompliant in debian. Reason: Vulnerability (PGV-2603774); No license detected <p>klibc-utils 2.0.14-1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603774); No license detected</p> ---- Begin: ---- libklibc 2.0.12-1 is Noncompliant in debian. Reason: Vulnerability (PGV-2603766); Vulnerability (PGV-2603774); Vulnerability (PGV-2603772); No license detected <p>libklibc 2.0.12-1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603766); Vulnerability (PGV-2603774); Vulnerability (PGV-2603772); No license detected</p> ---- Begin: ---- libklibc 2.0.14-1 is Noncompliant in debian. Reason: Vulnerability (PGV-2603774); No license detected <p>libklibc 2.0.14-1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603774); No license detected</p> ---- Begin: ---- libnss3 2:3.110-1+deb13u1 is Noncompliant in debian. Reason: Vulnerability (PGV-2616618); No license detected <p>libnss3 2:3.110-1+deb13u1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2616618); No license detected</p> ---- Begin: ---- libnss3 2:3.110-1+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2616618); No license detected <p>libnss3 2:3.110-1+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2616618); No license detected</p> ---- Begin: ---- libnss3 2:3.110-1 is Noncompliant in debian. Reason: Vulnerability (PGV-2616618); No license detected <p>libnss3 2:3.110-1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2616618); No license detected</p> ---- Begin: ---- libnss3 2:3.61-1+deb11u5 is Noncompliant in debian-bullseye-security. Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected <p>libnss3 2:3.61-1+deb11u5 is Noncompliant in debian-bullseye-security.</p> <p>Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected</p> ---- Begin: ---- libnss3 2:3.87.1-1+deb12u1 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected <p>libnss3 2:3.87.1-1+deb12u1 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected</p> ---- Begin: ---- libnss3 2:3.87.1-1+deb12u2 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected <p>libnss3 2:3.87.1-1+deb12u2 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected</p> ---- Begin: ---- libnss3-dev 2:3.110-1+deb13u1 is Noncompliant in debian. Reason: Vulnerability (PGV-2616618); No license detected <p>libnss3-dev 2:3.110-1+deb13u1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2616618); No license detected</p> ---- Begin: ---- libnss3-dev 2:3.110-1+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2616618); No license detected <p>libnss3-dev 2:3.110-1+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2616618); No license detected</p> ---- Begin: ---- libnss3-dev 2:3.87.1-1+deb12u2 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected <p>libnss3-dev 2:3.87.1-1+deb12u2 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2616923); Vulnerability (PGV-2616626); Vulnerability (PGV-2616618); Vulnerability (PGV-2616614); No license detected</p> ---- Begin: ---- libnss3-tools 2:3.110-1+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2616618); No license detected <p>libnss3-tools 2:3.110-1+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2616618); No license detected</p> ---- Begin: ---- libpng-dev 1.6.39-2+deb12u1 is Noncompliant in debian. Reason: Vulnerability (PGV-2603789); No license detected <p>libpng-dev 1.6.39-2+deb12u1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603789); No license detected</p> ---- Begin: ---- libpng-dev 1.6.39-2+deb12u3 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2603789); No license detected <p>libpng-dev 1.6.39-2+deb12u3 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2603789); No license detected</p> ---- Begin: ---- libpng-dev 1.6.39-2+deb12u4 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2603789); No license detected <p>libpng-dev 1.6.39-2+deb12u4 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2603789); No license detected</p> ---- Begin: ---- libpng-tools 1.6.39-2+deb12u3 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2603789); No license detected <p>libpng-tools 1.6.39-2+deb12u3 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2603789); No license detected</p> ---- Begin: ---- libpng-tools 1.6.39-2+deb12u4 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2603789); No license detected <p>libpng-tools 1.6.39-2+deb12u4 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2603789); No license detected</p> ---- Begin: ---- libsnmp40 5.9+dfsg-4+deb11u3 is Noncompliant in debian-bullseye-security. Reason: Vulnerability (PGV-2601834); No license detected <p>libsnmp40 5.9+dfsg-4+deb11u3 is Noncompliant in debian-bullseye-security.</p> <p>Reason: Vulnerability (PGV-2601834); No license detected</p> ---- Begin: ---- libsnmp40 5.9+dfsg-4+deb11u3 is Noncompliant in debian-bullseye-security. Reason: Vulnerability (PGV-2601834); No license detected <p>libsnmp40 5.9+dfsg-4+deb11u3 is Noncompliant in debian-bullseye-security.</p> <p>Reason: Vulnerability (PGV-2601834); No license detected</p> ---- Begin: ---- libsnmp40t64 5.9.4+dfsg-2+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2601826); No license detected <p>libsnmp40t64 5.9.4+dfsg-2+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2601826); No license detected</p> ---- Begin: ---- libsnmp40t64 5.9.4+dfsg-2 is Noncompliant in debian. Reason: Vulnerability (PGV-2601826); No license detected <p>libsnmp40t64 5.9.4+dfsg-2 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2601826); No license detected</p> ---- Begin: ---- libsnmp-base 5.9.3+dfsg-2+deb12u1 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected <p>libsnmp-base 5.9.3+dfsg-2+deb12u1 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected</p> ---- Begin: ---- libsnmp-base 5.9.3+dfsg-2 is Noncompliant in debian. Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected <p>libsnmp-base 5.9.3+dfsg-2 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected</p> ---- Begin: ---- libsnmp-base 5.9.4+dfsg-2+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2601826); No license detected <p>libsnmp-base 5.9.4+dfsg-2+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2601826); No license detected</p> ---- Begin: ---- libsnmp-base 5.9.4+dfsg-2 is Noncompliant in debian. Reason: Vulnerability (PGV-2601826); No license detected <p>libsnmp-base 5.9.4+dfsg-2 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2601826); No license detected</p> ---- Begin: ---- libsnmp-base 5.9+dfsg-4+deb11u3 is Noncompliant in debian-bullseye-security. Reason: Vulnerability (PGV-2601834); Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected <p>libsnmp-base 5.9+dfsg-4+deb11u3 is Noncompliant in debian-bullseye-security.</p> <p>Reason: Vulnerability (PGV-2601834); Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected</p> ---- Begin: ---- libtasn1-6 4.19.0-2+deb12u1 is Noncompliant in debian. Reason: Vulnerability (PGV-2603126); Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected <p>libtasn1-6 4.19.0-2+deb12u1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603126); Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected</p> ---- Begin: ---- libtasn1-6 4.19.0-2+deb12u1 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2603126); Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected <p>libtasn1-6 4.19.0-2+deb12u1 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2603126); Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected</p> ---- Begin: ---- libtasn1-6 4.19.0-3ubuntu0.24.04.2 is Noncompliant in ubuntu. Reason: Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected <p>libtasn1-6 4.19.0-3ubuntu0.24.04.2 is Noncompliant in ubuntu.</p> <p>Reason: Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected</p> ---- Begin: ---- libtasn1-6 4.20.0-2 is Noncompliant in debian. Reason: Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected <p>libtasn1-6 4.20.0-2 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2603138); Vulnerability (PGV-2603132); No license detected</p> ---- Begin: ---- python39-setuptools 44.1.1-150300.7.12.1 is Noncompliant in opensuse-update-sle-15.6. Reason: Vulnerability (PGV-2384240); No license detected <p>python39-setuptools 44.1.1-150300.7.12.1 is Noncompliant in opensuse-update-sle-15.6.</p> <p>Reason: Vulnerability (PGV-2384240); No license detected</p> ---- Begin: ---- python3-pil 11.1.0-5+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2612706); No license detected <p>python3-pil 11.1.0-5+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2612706); No license detected</p> ---- Begin: ---- python3-pil.imagetk 11.1.0-5+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2612706); No license detected <p>python3-pil.imagetk 11.1.0-5+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2612706); No license detected</p> ---- Begin: ---- snmp 5.9.3+dfsg-2+deb12u1 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected <p>snmp 5.9.3+dfsg-2+deb12u1 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected</p> ---- Begin: ---- snmp 5.9.3+dfsg-2 is Noncompliant in debian. Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected <p>snmp 5.9.3+dfsg-2 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2601826); Vulnerability (PGV-2601823); Vulnerability (PGV-2601820); No license detected</p> ---- Begin: ---- snmp 5.9.4+dfsg-2+deb13u1 is Noncompliant in debian-trixie-security. Reason: Vulnerability (PGV-2601826); No license detected <p>snmp 5.9.4+dfsg-2+deb13u1 is Noncompliant in debian-trixie-security.</p> <p>Reason: Vulnerability (PGV-2601826); No license detected</p> ---- Begin: ---- snmp 5.9.4+dfsg-2 is Noncompliant in debian. Reason: Vulnerability (PGV-2601826); No license detected <p>snmp 5.9.4+dfsg-2 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2601826); No license detected</p> ---- Begin: ---- telnet 0.17+2.4-2+deb12u1 is Noncompliant in debian. Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected <p>telnet 0.17+2.4-2+deb12u1 is Noncompliant in debian.</p> <p>Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected</p> ---- Begin: ---- telnet 0.17+2.4-2+deb12u2 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected <p>telnet 0.17+2.4-2+deb12u2 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected</p> ---- Begin: ---- telnet 0.17+2.4-2+deb12u3 is Noncompliant in debian-bookworm-security. Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected <p>telnet 0.17+2.4-2+deb12u3 is Noncompliant in debian-bookworm-security.</p> <p>Reason: Vulnerability (PGV-2608729); Vulnerability (PGV-2608720); No license detected</p>However these notifications of Non-compliant Packages have been done on April 11th.
-
RE: Increased Incorrect Classification of Security Vulnerabilitiesposted in Support
Hi,
Thanks for the response. We have the version 2025.25 (Build 11) with MSSQL
Those are just a few examples. However, there are more packages from Debian or other Feedstypes that are associated with security vulnerabilities from PyPi and NPM.
-
Increased Incorrect Classification of Security Vulnerabilitiesposted in Support
Hello There,
Since April 11, 2026 00:45:46, there have suddenly been several security vulnerabilities flagged as critical, even though their CVSS scores are well below 9.0.
For example, there are many Debian packages that have been blocked due to security vulnerabilities in PyPI or NPM.
Here are some screenshots illustrating this. Are these classifications really correct?
-
RE: How to use Package/Container Usage in ProGet/Otterposted in Support
I actually haven't looked into pgutil yet. I'll check it out.
But overall, ProGet does a pretty good job. Right now, I really can't think of anything that ProGet can solve uniquely.
-
RE: How to use Package/Container Usage in ProGet/Otterposted in Support
The intended use case is to improve the identification of vulnerable software packages in circulation.
This would allow me to determine which package(deb or rpm) on which host is at risk, thereby notifying the host owner and taking further action. However, the number of software packages on individual hosts can be very high.
On the Otter side, of course, systems can be administered with ease and an additional vault system. The use of inventoried configurations via groups and roles is particularly easy to implement. You wouldn’t need to learn any additional configuration or scripting language for this. You can, of course, learn OtterScript. But you don’t have to. It offers simple integration with Linux and Windows systems. Such a tool is particularly ideal for Windows server systems.
Perhaps you should continue to retain the usage/statistics in Proget. After all, the package/container scanner only needs JSON to feed the usage/statistics with information.
-
RE: How to use Package/Container Usage in ProGet/Otterposted in Support
Hi, thanks for the info.
We find this feature very interesting because packages can be tracked using Proget and Otter.
This allows users to check whether the packages they use have already been updated with the latest security updates.But it’s not a big deal if the feature is no longer supported soon.
It appears to be just a JSON interface that is used between Proget and Otter.
Btw. Offtopic
Can you take a look here again, I find it better to continue this thread instead of opening a new thread with the same topic:
https://forums.inedo.com/topic/5635/support-for-notautomatic-butautomaticupgrades-headers-in-debian-feed-release-files?_=1775537208917Thank you very much
-
RE: How to use Package/Container Usage in ProGet/Otterposted in Support
Additional Information:
proget[1916719]: Scan using Otter at http://otter/ failed: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.