LiveActive security incident?Get immediate response
CVE Record

CVE-2013-3703: No write permission check in change_role command

The controller of the Open Build Service API prior to version 2.4.4 is missing a write permission check, allowing an authenticated attacker to add or remove user roles from packages and/or project meta data.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Open Build Service allowed a logged-in user to add or remove package or project roles without proving they had write permission. In business terms, a lower-privileged account could potentially grant itself or others control over build metadata, creating risk to software integrity and access governance.

Executive priority

Treat as high priority where Open Build Service manages trusted software builds. The risk is not public unauthenticated compromise, but abuse of an authenticated account to alter role control over build projects or packages.

Technical view

CVE-2013-3703 is a missing authorization check in the Open Build Service API change_role command before version 2.4.4. The flaw maps to CWE-862 and is scored CVSS 3.0 8.8 because exploitation is network-reachable, low complexity, requires authentication, and can affect confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely in self-hosted or vendor-managed Open Build Service instances running versions before 2.4.4 with authenticated API users. The source bundle does not identify specific distributions, deployments, or CPEs beyond openSUSE Open Build Service.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The issue still matters because any authenticated account with API access could abuse missing authorization to alter roles on package or project metadata if the instance is vulnerable.

Researcher notes

Evidence is limited to the CVE description, SUSE Bugzilla reference, and upstream commit. The bundle names the fixed threshold as before 2.4.4 but does not provide exploit reports, affected CPEs, or downstream package status.

Mitigation direction

  • Upgrade Open Build Service to version 2.4.4 or later.
  • Review SUSE and Open Build Service guidance for deployment-specific fixes.
  • Restrict OBS API access to trusted authenticated users until remediated.
  • Audit package and project role assignments for unexpected changes.
  • Review logs for suspicious role additions or removals.

Validation and detection

  • Inventory Open Build Service instances and record their versions.
  • Confirm no exposed instance is running before version 2.4.4.
  • Verify change_role enforces write permission in the deployed code.
  • Run defensive regression tests for non-writer role changes.
  • Compare project and package metadata against known-good role baselines.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-3703 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.8High
CVSS 3.0 vector shape for CVE-2013-3703Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
openSUSEOpen Build ServiceunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.