Skip to content

the option --package_version not working as expected #15

@sebin-shajiphilip

Description

@sebin-shajiphilip

The flag exposed in vanir as "package_version" defined in vanir/detector_common_flags.py as:

One or more package versions your target code is under (e.g. for Android,
this can be "11", "12L", etc.). When given, signatures that are specific
to those versions will be used; signatures specific to other versions
will be ignored. If not given, no versions-specific signatures will be
used...

But when called with this flag( --package_version=10,11) as:

./bazel-bin/detector_runner --target_selection_strategy all_files offline_directory_scanner /srv/scratch/sipp/idcevo-samsung_v9x0-pu2511/Android/packages/services/Telephony/src/com/android/phone/settings/ --vulnerability_file_name ../CVE-2025-32346.json --package_version=10,11

, it still flags CVE-2025-32346 as unpatched (although the two "versions" in the "affected" entry of the OSV json file (downloaded from https://osv.dev/vulnerability/ASB-A-337785563) is defined as '16' and '16-next'). Which means the option --package_version is not working or not properly implemented

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions