macvim-dev / macvim-dev/macvim
Reconcile version #'ing system
Nobody has claimed this yet.
- Dominant language
- Vim Script
- Stars
- 7.9k
- Forks
- 691
- PR merge metrics
- No merged PRs in 30d
Description
Hello, my company uses an endpoint software monitoring system to ensure apps are updated to avoid vulnerabilities.
This version:
Is being reported as suffering from:
https://www.cve.org/CVERecord?id=CVE-2023-41036 and
https://nvd.nist.gov/vuln/detail/CVE-2023-41036
(Both are the same.)
I believe the version reported by MacOS:
Leads the endpoint monitoring software to see this as behind release 178.
I understand that the versioning may be due to “stuff”. However, this legacy practice brings extra unwanted attention. If efforts can be made to improve this, I’m sure others will be appreciative as well.
Thank you,
David Halonen
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by comparing the MacVim version reported by macOS with release 178 and trace how the project’s version is defined and published; done means the endpoint monitoring system no longer identifies the current release as affected by CVE-2023-41036.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, vim
- Domain
- desktop, release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100