CVE-2021-27614
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSAP Business One Hana Chef Cookbook, versions - 8.82, 9.0, 9.1, 9.2, 9.3, 10.0, used to install SAP Business One on SAP HANA, allows an attacker to inject code that can be executed by the application. An attacker could thereby control the behaviour of the application thereby highly impacting the integrity and availability of the application.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCode injection vulnerability in SAP Business One Hana Chef Cookbook allows attackers to inject malicious code during the SAP Business One installation process on SAP HANA. The injected code executes with application privileges, enabling control over application behavior and compromising integrity and availability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.1.6= 0.1.7= 0.1.19= 8.82= 9.0= 9.1= 9.2= 9.3= 10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the SAP Business One Hana Chef Cookbook installationSearch for the Chef Cookbook directory or files related to SAP Business One deployment on the system. Check common Chef cookbook paths such as /cookbooks, ~/chef-repo/cookbooks, or the directory where the cookbook was extracted during installation.Affected if The Chef Cookbook for SAP Business One Hana is found on the system and is actively used for deployment or configuration.
-
Identify the installed Chef Cookbook versionExamine the cookbook's metadata.rb, metadata.json, or version file within the cookbook directory. Look for a version declaration such as 'version 0.1.6', 'version 0.1.7', or 'version 0.1.19'.Affected if The cookbook version is exactly 0.1.6, 0.1.7, or 0.1.19.
-
Check SAP Business One installation versionRun the SAP Business One version check command or inspect the installed SAP Business One components on the system. This may be found in the installation directory, registry, or via SAP management tools.Affected if SAP Business One version is 8.82, 9.0, 9.1, 9.2, 9.3, or 10.0.
-
Verify the cookbook is used in the deployment processReview Chef run lists, recipes, or deployment scripts that reference the SAP Business One cookbook. Determine if the cookbook is actively executed during SAP Business One installation or configuration.Affected if The vulnerable cookbook version is included in a Chef run list or recipe used for SAP Business One deployment.
The environment is affected if the SAP Business One Hana Chef Cookbook version 0.1.6, 0.1.7, or 0.1.19 is installed and actively used for deploying SAP Business One versions 8.82 through 10.0.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of the Chef Cookbook when available, or perform input validation/sanitization on all parameters within the cookbook recipes before execution.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-27614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data