Skip to content

Apache HTTPD does NOT use Maven versioning #579

Description

@pombredanne

The current code use the univers MavenVersion for httpd advisories. This is incorrect.
The semantics and range notation from httpd are NOT the Maven ones.
See https://httpd.apache.org/security/json/CVE-2000-1204.json for instance:

  "affects": {
    "vendor": {
      "vendor_data": [
        {
          "vendor_name": "Apache Software Foundation",
          "product": {
            "product_data": [
              {
                "product_name": "Apache HTTP Server",
                "version": {
                  "version_data": [
                    {
                      "version_name": "1.3",
                      "version_affected": "=",
                      "version_value": "1.3.12"
                    },
                    {
                      "version_name": "1.3",
                      "version_affected": "=",
                      "version_value": "1.3.11"
                    },
                    {
                      "version_name": "1.3",
                      "version_affected": "=",
                      "version_value": "1.3.9"
                    }
                  ]
                }
              }
            ]
          }
        }
      ]
    }

And per https://archive.apache.org/dist/httpd/ the version seem to be mostly semver with some pre-release extra but these is NOT maven.

Activity

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