CVE-2024-2331
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 · uneditedA vulnerability was found in SourceCodester Tourist Reservation System 1.0. It has been declared as critical. This vulnerability affects the function ad_writedata of the file System.cpp. The manipulation of the argument ad_code leads to buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-256282 is the identifier assigned to this vulnerability.
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 confidenceBuffer overflow vulnerability in SourceCodester Tourist Reservation System 1.0's ad_writedata function in System.cpp. The ad_code argument is not properly bounds-checked before being written to a fixed-size buffer, allowing an attacker to overwrite adjacent memory when providing an overly long ad_code value.
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= 1.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Confirm Tourist Reservation System installationCheck if Razormist Tourist Reservation System version 1.0 is installed on the system. Look for the application in installed programs list, program files directory, or search for executable files related to the tourist reservation system.Affected if The application is Razormist Tourist Reservation System version 1.0 exactly
-
Locate the vulnerable System.cpp componentSearch for System.cpp or compiled binaries that contain the ad_writedata function. Check the application installation directory for source code or DLL/EXE files that may contain this function.Affected if System.cpp or a compiled binary containing ad_writedata is present in the application
-
Identify ad_code input mechanismDetermine how the ad_code value is provided to the application. This could be through a form field, configuration file, API parameter, or direct database entry in the reservation system.Affected if The application accepts ad_code input through any user-controllable interface
-
Test for long ad_code input handlingSubmit or provide an ad_code value exceeding typical length limits (for example, more than 256 characters) through the identified input mechanism and observe if the application handles it without crashing or showing signs of memory corruption.Affected if The application accepts overly long ad_code values without proper bounds checking
A user is affected if they have Razormist Tourist Reservation System version 1.0 installed and the application accepts ad_code input that can be provided in overly long values without validation.
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 dataImplement proper bounds checking on the ad_code input and replace unsafe string operations (strcpy, strcat, sprintf, etc.) with safe alternatives (strncpy, snprintf, or std::string). If a patched version is available from the vendor, upgrading is recommended.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2331 — 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-2024-2331 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